Orbitor Gateway (IPFS)
Background
The Infrastructure team operates the IPFS HTTP Gateway infrastructure (Orbitor) to provide public access to IPFS content via standard HTTP. The backend gateway is Rainbow, an implementation of the IPFS HTTP Gateway API based on Boxo, the tooling that powers the Kubo IPFS implementation. It uses the same Go code as Kubo’s HTTP gateway but is fully specialized to serve as a gateway.
The Infrastructure team runs multiple Rainbow gateways and dedicated backend peer nodes across multiple regions for high availability and low-latency global coverage.
- Global endpoint: https://ipfs.orbitor.dev/
- EU endpoint: https://eu.orbitor.dev/
- LATAM endpoint: https://latam.orbitor.dev/
- APAC endpoint: https://apac.orbitor.dev/
In addition to our internal monitoring tools, we host the following public monitoring endpoints for visibility and reach:
Architecture
The Orbitor gateway infrastructure consists of:
- IPFS gateway: running Rainbow gateway software
- IPFS node: running Kubo software
- Cloudflare global load balancing: for high availability and traffic steering
- Observability Stack: Prometheus, Grafana, Alertmanager, PagerDuty, Betterstack, Grafana K6...
Below is the architecture overview of the global endpoint.

Deployment & Maintenance
IPFS execution configuration:
IPFS-related Ansible roles:
- Kubo node: https://github.com/ChainSafe/ansible-collection/tree/main/roles/ipfs_node_docker_role
- Rainbow Gateway: https://github.com/ChainSafe/ansible-collection/tree/main/roles/ipfs_gateway_docker_role
Deployment/Upgrade Steps
-
Get the latest image tag
-
Rainbow Gateway:
-
Kubo Node:
-
-
Update the image tag in the Ansible configuration
-
Dry-run the deployment with
--check:- Rainbow Gateway:
ansible-playbook ./playbooks/start-ipfs-gateway.yml -l ipfs-gateway --diff --check- Kubo node:
ansible-playbook ./playbooks/start-ipfs-node.yml -l ipfs-node --diff --check -
Deploy the changes once acceptable
-
Verify the gateway is operational
- Check container logs
- Verify dashboards/status