> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avrxt.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding website status

> Read AVRXT service availability, public incidents, maintenance, and gaps in monitoring history.

Open [avrxt.dev/status](https://www.avrxt.dev/status) for the website’s public status view. The independent [hosted status page](https://status.avrxt.dev) is a fallback when the website itself is unavailable.

## What is reported

The website reads public Better Stack feeds and displays whitelisted resources, reports, and updates. A source failure is shown as **unknown** rather than healthy. Internal incident notes are not part of the public feed.

## Freshness

The browser updates approximately every five minutes while visible and when returning to the tab. Public server reads use a short cache. This is not a second-by-second monitoring console.

## Reading history correctly

A history gap means monitoring data is absent. Manually reported entries are distinct from measured uptime. Neither should be turned into an invented uptime percentage.

## Reporting a problem

Include a public URL, approximate time, browser, and a short reproduction. Distinguish the main website, profile, docs, and Muzix hostnames; they may be deployed separately. Do not include monitoring bearer tokens or internal provider records.

## Related reading

* [Status API](https://docs.avrxt.dev/api-reference/status.md)
* [Troubleshooting](https://docs.avrxt.dev/maintaining/troubleshooting.md)
* [Deployment boundaries](https://docs.avrxt.dev/maintaining/deployment.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.