How to read Gatsby’s status cards
The status view describes whether public endpoints associated with Gatsby responded during a dated check. It is a technical snapshot, not a statement about the framework’s quality, maintenance, or future availability.
What each card means
| Card | Visitor-facing interpretation |
|---|---|
| HTTP | The website returned a web response when checked. A successful code means the requested page was reachable at that moment. Redirects show that the browser was sent to another URL. |
| TLS | The HTTPS connection presented a certificate that could be validated during the check. This concerns encrypted transport and certificate handling, not the accuracy of page content. |
| DNS | The hostname resolved to network records during the check. Resolution confirms that the name could be located then, but it does not guarantee every visitor or region had the same result. |
A successful HTTP result can coexist with a broken documentation route, missing asset, or application error elsewhere. Likewise, one unsuccessful request can reflect temporary maintenance, a network path, or a specific page problem rather than a domain-wide outage.
What to do when a card shows a problem
- Open gatsbyjs.com directly and retry the relevant documentation page.
- Confirm that the browser is using the expected HTTPS hostname.
- Check whether only one route is affected or the official site is broadly unavailable.
- Use the official Gatsby repository when documentation access is interrupted.
- Recheck later before drawing conclusions from a single dated observation.
Status cards are intentionally narrow. They describe observable web connectivity at a recorded time and should be read alongside the timestamp shown in the interface.
