Global Incident - Pre-Recorded / Real-Time
critical- Started
- Sep 23, 3:05 AM EDT
- Resolved
- Sep 23, 4:10 AM EDT
- Duration
- 1h 4m
Gladia's updates (4)
- investigating · Sep 23, 3:05 AM EDT
Investigating source of the issue
- investigating · Sep 23, 3:14 AM EDT
Still Investigating source of the issue.
- monitoring · Sep 23, 3:33 AM EDT
Update : service recovering Situation returning to normal. New Pre-Recorded jobs process normally. Jobs from 08:55–09:34 UTC+2 are processed with delay.
- resolved · Sep 23, 4:10 AM EDT
All services have returned to normal operation. The provider-side network issue is resolved. New jobs are processing normally, and the remaining Pre-Recorded backlog from this morning has been cleared. We consider this incident resolved. Thank you for your patience.
What our checks recorded
We checked Gladia 12 times from Gladia's start time to its resolution, once every five minutes. Every one of them reached Gladia's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 90 ms, against 120 ms over the 24 hours before. Gladia posted the incident at Sep 23, 3:05 AM EDT.
Updates are Gladia's own words from its status page (status: resolved); we never add an inferred cause.