RPC is first-class. Control plane and data services are probe-backed.
Swivy
Status for RPC, control plane, and blockchain data.
This page is the public systems surface for Swivy. It keeps the RPC edge, customer control plane, and blockchain data services in one place while the actual multichain gateway stays on a long-lived host built for HTTP and websocket traffic.
Primary RPC target
Gateway base URLhttps://rpc.swivy.dev
LivenessUpstream responded with 503.
ReadinessUpstream responded with 503.
ProviderUpstream responded with 503.
Last checked: 7/17/2026, 10:23:19 PM
Public systems currently reporting fully healthy states.
Live matrix sourced from the gateway provider contract.
Networks advertising websocket transport through the public contract.
System
RPC infrastructure
Public EVM and Solana RPC ingress, websocket transport, project auth, and provider discovery.
Base URLhttps://rpc.swivy.dev
Upstream responded with 503.
LivenessUpstream responded with 503.
ReadinessUpstream responded with 503.
ProviderUpstream responded with 503.
System
Swivy control plane
Account auth, customer control plane, and operator surfaces that sit alongside the RPC edge.
Base URLhttps://rpc.swivy.dev
Upstream responded with 503.
HealthHTTP 503
ReadinessHTTP 503
System
Blockchain data
Indexed chain data, explorer-grade reads, and other non-RPC delivery surfaces.
Base URLNot configured yet
Waiting for a base URL before live checks can start.
SetupSet BLOCKCHAIN_DATA_BASE_URL to enable checks.
RPC detail
Live transport availability
No network data is available yet. Once the gateway is configured, this page will render the provider metadata and live status feeds.
RPC contract
What integrators connect to
HTTP RPCConfigure the gateway first
WebSocket RPCConfigure the gateway first
Provider statusUnavailable until the gateway URL is set
Why this split works
Public status in front of multiple Swivy systems.
Vercel status app
- Public landing page, status, and RPC docs
- Live reads from the same contract Swivy clients consume
- Safe place to add more product-system visibility over time
RPC edge
- HTTP and websocket RPC ingress
- Project auth, usage, limits, and upstream failover
- Prometheus metrics and readiness gating
Other Swivy services
- Control plane and auth can surface through probe-backed cards
- Blockchain data APIs can be added without rewriting the page
- The homepage stays useful even while each system matures separately