G
Outage recap · Gladia

Gladia outage — September 14, 2026

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

[Europe] API is in a degraded state

minor
Started
Sep 14, 5:07 AM EDT
Resolved
Sep 14, 12:38 PM EDT
Duration
7h 31m

Gladia's updates (11)

  1. investigating · Sep 14, 5:07 AM EDT

    We are currently experiencing degraded performance on our Europe API. 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.

  2. monitoring · Sep 14, 6:18 AM EDT

    We are currently experiencing degraded performance on our Europe API. 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.

  3. monitoring · Sep 14, 6:36 AM EDT

    We have identified the root cause: an external tool generated a traffic spike and a network incident. This delayed transcription processing and impacted our network, which also explains the upload latency. Service is progressively returning to normal. We continue to monitor and will share a final update once everything is confirmed stable.

  4. monitoring · Sep 14, 9:02 AM EDT

    The network issue is now fully resolved. Uploads and API submissions should work normally again. We are still clearing the backlog that built up during the disruption, and we are working to catch up. New jobs are typically completing in around **5 minutes**. Jobs that were already waiting, or accounts with a large queue, can still see longer processing times until that backlog drains. We will keep monitoring and share another update as processing returns to normal.

  5. monitoring · Sep 14, 11:01 AM EDT

    Uploads are working normally again. Processing capacity is still reduced while we clear the backlog from earlier today. Expect around **3 minutes** for new jobs during peak periods, and longer (up to about **20 minutes**) if you have a high volume waiting in the queue. We are continuing to improve capacity and will update again as times return to normal.

  6. resolved · Sep 14, 12:38 PM EDT

    Incident is now resolved. The average transcription time is less than 1 minute

  7. monitoring · Sep 15, 6:09 AM EDT

    We are still facing performance issues, requests might take a few minutes to be processed.

  8. monitoring · Sep 15, 7:51 AM EDT

    We are still facing performance issues due to reduced infrastructure capacity. Processing times vary by account: they depend on your current transcription queue and your concurrent processing limit. Across all accounts, average turnaround is currently around 22 minutes. All transcriptions are still being processed and are not lost. Some may simply complete more slowly than usual. Our teams continue to work on restoring full capacity.

  9. monitoring · Sep 15, 9:13 AM EDT

    We are still facing performance issues due to reduced infrastructure capacity, but average processing times have improved. Across all accounts, average turnaround is currently around 12 minutes. Actual times still vary by account depending on your current transcription queue and your concurrent processing limit. All transcriptions are still being processed. Some may simply complete more slowly than usual. Our teams continue to work on restoring full capacity.

  10. monitoring · Sep 15, 9:58 AM EDT

    We are still facing performance issues due to reduced infrastructure capacity, average processing times have degraded. Across all accounts, average turnaround is currently around 28 minutes. Actual times still vary by account depending on your current transcription queue and your concurrent processing limit. All transcriptions are still being processed. Some may simply complete more slowly than usual. Our teams continue to work on restoring full capacity.

  11. resolved · Sep 15, 6:38 PM EDT

    Processing queues are empty and pre-recorded transcription processing times are back to normal. Real-time and live streaming sessions are operating normally. During this incident, some customers experienced elevated error rates, timeouts, and degraded processing times on pre-recorded, real-time, and live streaming endpoints. A detailed post-mortem will be shared in the coming days. We sincerely apologize for the disruption and thank you for your patience.

What our checks recorded

We checked Gladia 90 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 174 ms, against 166 ms over the 24 hours before. Gladia posted the incident at Sep 14, 5:07 AM EDT.

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.