Ashby: vendor-reported minor incident on September 22 (tracked 3d 0h)
Sep 22, 03:00 PM → Sep 25, 03:05 PM · 3d 0h · medium
Ashby reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3d 0h, from Tue, 22 Sep 2026 15:00:01 GMT to Fri, 25 Sep 2026 15:05:11 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
This incident affected Ashby for approximately 3 days, from September 22 to September 25. The severity of the incident was classified as medium. No user-reported data was collected for this incident, and impact was assessed based solely on automated signals.
Incident timeline
- Sep 22, 03:00 PM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
- Sep 22, 03:00 PM
Status updated: possible issue
- Sep 25, 03:05 PM
PulseWatch closed the incident
Official updates
- Sep 22, 03:00 PM
Ashby reported the incident on its status page.
View official source