# SQD Portal status

> Live status of SQD Portal, the HTTP API that serves blockchain data for over 100 networks. It says whether the portal answers, whether each network's real-time data keeps up with its chain, and whether requests are being rate limited.

The web page at `/` is drawn in the browser, so fetching it returns an empty shell. Read the Markdown below instead. Links that start with `/` are on this site.

## Current status

- [Public plan](/status.md): Status of `portal.sqd.dev`, the portal that needs no API key. About 8 KB of Markdown, rebuilt at most once a minute.
- [Starter and Growth plans](/status.md?service=shared): Status of the portal behind Starter and Growth API keys. Same layout.
- [One network](/status.md?network=base-mainnet): Put a dataset id after `network=`, and add `&service=shared` for the other portal. About 1 KB: the network's state, uptime, latest block age and its issues of the last 90 days. An id that does not exist answers 404 with the nearest ones.

Each one has the portal's own rows, the open issues, a table of measured networks with state and uptime, the networks that are not real-time yet, and the issues that ended in the last 7 days.

## When to read it

- A Portal request fails with a 5xx, or a stream stops receiving new blocks. Look at "Open issues" and at the network's row.
- A request is answered with HTTP 529 and the code `overloaded`. That is rate limiting, the Capacity row. Wait the number of seconds in `Retry-After`, then retry.
- A network's data ends hours or days before the chain head. Check whether the network is listed under "Not real-time yet". For those networks that is expected.

## Terms

- **Real-time data**: new blocks at the chain head.
- **Historical data**: past blocks, served from SQD Network.
- **Capacity**: whether the portal is refusing requests because it is at its limit. "Rate limited" means about 5% or more of requests in a five-minute window were refused with `overloaded`. "Heavily rate limited" means half or more were. The data is unaffected, so the portal still counts as operational while it rate limits.
- **Measured network**: a real-time network with an uptime figure of its own.
- **Not real-time yet**: a network the portal serves from SQD Network alone, so its newest data is hours or days behind the chain. This is how it is served for now, not a fault.
- **Latest block age**: how old the newest block the portal serves for a network was when it was last measured.
- **Uptime**: the share of measured time without an outage. For Capacity it is the share of time not heavily rate limited.
- **States**: Operational, Degraded, Outage, Maintenance, No data.
- **Groups**: Core, Partner, Frontier and Testnet. A network's dataset id, such as `base-mainnet`, is what goes in a Portal URL.

## Raw data

- [Public plan snapshot](https://status-snapshots.sqd.dev/services/public.json): Everything the page draws, as JSON, republished every minute. About 1 MB, so filter it with a tool instead of reading it whole. For example `jq '.components[] | {dataset: .component.key, state}'`.
- [Starter and Growth snapshot](https://status-snapshots.sqd.dev/services/shared.json): The same for the other portal.
- [Networks the public portal serves](https://portal.sqd.dev/datasets): JSON. `real_time` says whether a network is real-time.

## Optional

- [SQD documentation for agents](https://docs.sqd.dev/llms.txt): How to query the Portal.
- [How the portal serves data](https://docs.sqd.dev/en/portal/introduction/how-portal-serves-data): The two sources a portal reads from, and why one runs behind the chain.
- [Error handling](https://docs.sqd.dev/en/portal/introduction/error-handling): The error envelope, the `overloaded` answer and when to retry.