Service status

How we measure uptime

Reporting window

Rolling 90 days, aggregated by calendar day

Operational

Error rate and latency both within thresholds

Degraded latency

Latency over threshold, requests still succeed

Unavailable

Failed to serve requests for 5+ minutes straight

Not monitored

This component isn't monitored yet

How it's calculated

Successful requests / valid requests. Failed requests aren't billed, but still count toward uptime.

Where our responsibility ends

This page reflects ChainBridge service availability only. It makes no guarantee about the state of any blockchain network.

• Congestion, reorgs, or outages on upstream chains aren't ChainBridge outages. We document the impact in each incident.
• ChainBridge never custodies assets, asks for private keys, signs on your behalf, or promises to recover lost funds.
• Uptime commitments follow your plan or contract.
• Planned maintenance is announced ahead of time. Emergency maintenance gets a post-incident review.

Subscribe to status updates

Receive status changes and security advisories by webhook, or by email.

Found an issue?

If you hit something this page doesn't show, file a ticket with your X-Request-Id and when it happened so we can check the logs.

Security advisories

Vulnerability incidents and risk-label changes also go out on the security page. Every advisory keeps its source, reviewer, and last-updated time.