Access Hub status
Collecting data
Refreshes every 60 s
Services
Measured now
| Service | What it covers | State |
|---|---|---|
| Recent data | Current state and recent ledgers. Most applications only ever need these. | Collecting data |
| Full history | Any ledger the hub has to fetch from the full-history servers. It happens automatically; you send the same request either way. | Collecting data |
| Peer protocol | Reserved connections for nodes that peer with the hub. | Collecting data |
Traffic
Requests served per minute · last 24 hours · UTC
- Served
- Collecting data
- Turned away (429)
- Collecting data
- Server errors (5xx)
- Collecting data
- Served
- Turned away (429)
Peering
Connections to the hub · last 24 hours
Collecting data
- Connections
- No reading
About these figures
Every figure on this page is measured on the hub's own load balancers and republished once a minute. Traffic and rates cover the last 24 hours; the response times cover the last hour.
Peer connections are connections, not peers. A node connected to the hub twice is counted twice, and the figure is a count at this moment rather than an average.
The peering chart is sampled every 30 minutes. A gap is a half hour with no reading, not a half hour with no peers.
The two percentages have different denominators, so each names its own: the server-error share is of the requests we served, and the limit share is of everything that arrived, turned-away requests included.
Uptime history and past incidents are not published yet. The services above report the state measured right now.
Some of the hub's connection slots are reserved for nodes that need a guaranteed link. To reserve one, see Keys and peering.