G
Outage recap · Gladia

Gladia outage — September 23, 2026

On September 23, 2026, Gladia had 4 reported incidents on Gladia's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

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)

  1. investigating · Sep 23, 3:05 AM EDT

    Investigating source of the issue

  2. investigating · Sep 23, 3:14 AM EDT

    Still Investigating source of the issue.

  3. 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.

  4. 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.

[Europe] Pre-Recorded is in a degraded state

minor
Started
Sep 23, 3:29 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Gladia 24 times in the two hours after Gladia's start time (it published no end time), 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 118 ms, against 120 ms over the 24 hours before. Gladia's feed showed the incident by Sep 23, 3:35 AM EDT (we read it every five minutes).

Updates are Gladia's own words from its status page (status: resolved); we never add an inferred cause.

Real-time and Pre-recorded is having issue

minor
Started
Sep 23, 10:14 AM EDT
Resolved
Sep 23, 11:47 AM EDT
Duration
1h 33m

Gladia's updates (6)

  1. investigating · Sep 23, 10:14 AM EDT

    Another network incident is affecting our production

  2. investigating · Sep 23, 10:24 AM EDT

    Investigating source of the issue

  3. identified · Sep 23, 10:35 AM EDT

    Network issue affecting Pre-recorded and Real Time. Transcription processing is slower than usual, and file uploads may also be affected. Our team is actively working on a resolution. We will share another update as soon as more information is available.

  4. identified · Sep 23, 10:36 AM EDT

    Network issue affecting Pre-recorded and Real Time. Transcription processing is slower than usual, and file uploads may also be affected. Our team is actively working on a resolution. We will share another update as soon as more information is available.

  5. monitoring · Sep 23, 10:53 AM EDT

    The underlying issue has been mitigated and the platform is stable again. Pre-recorded transcriptions are still taking around 6 minutes on average as we work through the backlog accumulated during the incident. We are monitoring closely and will share another update once processing times return to normal.

  6. resolved · Sep 23, 11:47 AM EDT

    The network issue reported by our provider has been resolved, and the platform is stable again. We scaled processing capacity to clear the backlog accumulated during the incident, and the queue is now fully drained. Pre-recorded processing times have returned to an average of around 15 seconds. Real-Time is stable.

What our checks recorded

We checked Gladia 19 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 109 ms, against 126 ms over the 24 hours before. Gladia posted the incident at Sep 23, 10:14 AM EDT.

Updates are Gladia's own words from its status page (status: resolved); we never add an inferred cause.

[Europe] Pre-Recorded is in a degraded state

minor
Started
Sep 23, 10:19 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Gladia 24 times in the two hours after Gladia's start time (it published no end time), 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 117 ms, against 126 ms over the 24 hours before. Gladia's feed showed the incident by Sep 23, 10:25 AM EDT (we read it every five minutes).

Updates are Gladia's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Gladia. This recap summarizes incidents published on Gladia's official status page.