Today-specific status answer for the query population looking for a same-day signal.
As of , the platform is operational. The current day's probe history is reproduced in the homepage 90-day uptime bars (the rightmost segment); the prior 24 hours show no full-mirror outages. The tertiary mirror is in degraded latency mode for the third consecutive day, an issue that traces to a slow guard rotation on the Tor network rather than a platform-side fault.
If you noticed an outage that the public probe missed, file a brief note via the editorial newsroom's onion mirror. The probe operates from a single set of vantage points and can miss localised reachability problems that the platform itself is not experiencing.
A single slow day means little on its own. What matters is whether today looks different from the last few weeks on the same mirrors. A mirror that has been degraded for a fortnight is not having a bad day, it is in its normal condition and the label has stopped being informative.
Hidden services get busy in waves and a mirror that crawls in one part of the day answers instantly in another. If something was unusable earlier, trying again a few hours later is a genuine fix rather than superstition.
Open another onion service. That single test separates a problem at the platform from a problem in your own client, and it takes twenty seconds. Almost everybody skips it and then spends an hour on the wrong side of the connection.
All mirrors failing the same way, with the same error, for hours. That is worth waiting out rather than working around, and it clears on its own far more often than not.
Component states, the 90 day uptime history and the incident log live on the status dashboard. This page covers one question in depth rather than repeating the board.