Auto-drafted postmortem
Tabby: vendor-reported critical incident on October 3 (tracked 1h 12m)
Oct 3, 01:14 PM → Oct 3, 02:26 PM · 1h 12m · high
Tabby reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1 hour and 12 minutes, closing it on October 3, 2026, at 2:26 PM UTC.
Duration
1h 12m
tracked by PulseWatch
Impact
PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. The incident is known from Tabby's own status page, which declared a critical-impact outage.
Incident timeline
- Oct 3, 01:14 PM
The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it
- Oct 3, 01:14 PM
Status updated: possible issue
- Oct 3, 02:26 PM
PulseWatch closed the incident
Official updates
- Oct 3, 01:14 PM
Tabby reported the incident on its status page.
View official source