← Back to Unit's check readings
We started checking Unit on November 2, 2026, which is 8 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when our checks of Unit fail from two or more distant regions
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Unit's own status page declared. Below it, any public chatter we saw about Unit and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Unit's own status page declared. Three records side by side; none of them changes another.
- Elevated API Errors: partial outage, from 07:00 UTC to 07:15 UTC.
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Unit's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Unit next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
- Bluesky posts1 in the last hour (prior day averaged 0.4/hour)
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Checks passing | Probes recorded |
|---|---|---|
| US-East | 100.00% | 867 |
| US-West | 99.86% | 709 |
| Europe | 100.00% | 664 |
| Asia-Pacific | 100.00% | 398 |
Monthly summary
Tracking Unit since Nov 2, 2026. In that time our checks failed from two or more distant regions in no probe event. Months before that date are not tracked and carry no figure.
| Month | Uptime by our checks | Probe events | Time failing |
|---|---|---|---|
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 | not tracked | ||
| Sep 2026 | not tracked | ||
| Oct 2026 | not tracked | ||
| Nov 2026 from Nov 2, 2026 | 100% | 0 | 0 min |
Uptime by our checks is the share of each month in which no probe event was open for Unit. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Unit's own status page contribute nothing to these figures.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime.
Our probe event log
Every probe event for Unit in the last 90 days, or since we started checking it if that is more recent. This list is probe-only: Unit's own declared incidents appear further down this page in their own attributed section, never merged with what our checks show here. User reports live on the live page, in their own labeled block.
Their declared record
Unit's own incident history, taken from their public status feed. This is their account of what happened, not our check reading, and it never changes the event log above or the other way around.
Showing the 10 most recent of 51 incidents Unit has declared in the history we hold.
These entries are Unit's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
The scorecard
How Unit's status page compared with our check readings, for every probe event above that falls inside the window we have been capturing their claims.
We started recording Unit's own status page on November 2, 2026, 6 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside probe events from our own checks.
Unit decides what their status page covers, and it may report per component while our checks request one surface from ten regions. We state what each side reported and leave the conclusion to you. If Unit believes a figure here is wrong, we publish corrections as prominently as the original.
Full detail on what a probe does and does not prove is in the methodology page.