Reading the current status cards
The HTTP, TLS, and DNS cards describe what the Astro website returned or exposed when the displayed checks were made. Read their timestamps and individual results together: one successful card does not prove that every page, network, or future visit will behave identically.
| Card | What it can indicate | What it cannot establish |
|---|---|---|
| HTTP | Whether a web request received a response and, when shown, its response category | That every route, asset, or visitor session works |
| TLS | Whether the checked connection presented usable HTTPS information | Permanent security or uninterrupted certificate renewal |
| DNS | Whether the domain resolved during the displayed check | That every resolver or region currently has the same answer |
A normal HTTP result suggests the checked endpoint was reachable at that moment. Redirects can also be intentional, while client or server error responses deserve investigation in the context of the requested URL.
Troubleshooting a visit
If the website is not loading for you, first compare your experience with all three cards. A healthy-looking DNS result alongside an HTTP error points toward a different problem than a domain that does not resolve.
Try these practical checks:
- Open the official address directly: astro.build.
- Confirm that the browser address uses
https://and has no misspelling or unexpected subdomain. - Reload once, then try a private window to rule out stale browser state or an extension conflict.
- Test another network or DNS resolver if name resolution appears to be the problem.
- If one documentation page fails, try the documentation home before assuming the entire site is unavailable.
- Record the exact URL, time, browser message, and HTTP status before asking for help.
Interpreting mixed results
A working homepage does not guarantee that documentation, package downloads, GitHub, or Discord are reachable because those resources may use separate services and domains. Conversely, a local browser failure does not by itself show that Astro’s official site is broadly unavailable.
Use the cards as current diagnostic clues, not uptime promises. For persistent issues, consult Astro’s official website, maintained GitHub repository, or community support link and include the specific evidence you observed.
