Rev.ai

Affected: Streaming Speech to Text API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 21:54 UTC

   We are currently investigating an issue where streaming transcription sessions using multi-channel audio (stereo or more channels) are failing to return transcriptions. Sessions using standard single-channel audio (mono PCM16 at 16kHz) are not affected. Our team has identified...

2. resolved 2026-05-13 22:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-16 17:37 UTC

   We are currently investigating this issue.

2. investigating 2026-04-16 17:37 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-04-16 19:41 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-16 20:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-11 04:15 UTC

   At 7/10/2024 9:15 PM PT there is a minor outage affecting a small percentage of non-English speech to text jobs that caused the jobs to fail and/or incurred a delay in the jobs' turn around times. All operations were resumed back to normal by 10:10 PM PT.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API, Streaming Speech to Text API, RTMP Ingestion, Custom Vocabulary API, Topic Extraction API, Sentiment Analysis API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-06-09 17:46 UTC

   We are experiencing network issues between our internal services. Issue is identified and investigation of a fix is ongoing

2. monitoring 2023-06-09 18:09 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2023-06-09 18:11 UTC

   We are continuing to monitor for any further issues.

4. resolved 2023-06-09 18:15 UTC

   This incident has been resolved. A postmortem will be coming by EOD

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API, Streaming Speech to Text API, RTMP Ingestion, Custom Vocabulary API, On-Prem Licensing Server, Topic Extraction API, Sentiment Analysis API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-01-06 20:07 UTC

   We are currently investigating this issue.

2. investigating 2023-01-06 20:07 UTC

   We are continuing to investigate this issue.

3. resolved 2023-01-06 20:15 UTC

   The event was momentary and lasted only for a small number of requests in a duration less than 30 seconds. It's unlikely that any customer has noticed a degradation in TaT for any service. Streaming API connections may have been terminated by the server or partial/final...

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2022-09-28 18:02 UTC

   Issue is caused by AWS Service outage. https://health.aws.amazon.com/health/status

2. identified 2022-09-28 19:18 UTC

   The issue has been identified as an issue with AWS https://health.aws.amazon.com/health/status

3. resolved 2022-09-28 21:20 UTC

   AWS is showing that the incident has been resolved. Our engineering team is continuing to monitor this situation, but we have observed improvements on transcription turn around times.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Streaming Speech to Text API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-09-27 18:47 UTC

   We are currently investigating this issue.

2. identified 2022-09-27 18:47 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2022-09-27 20:01 UTC

   This incident has been resolved.

4. postmortem 2022-09-27 20:01 UTC

   We opened the incident out of an abundance of caution. Our automated systems fixed the issue before it reached any customers. No impact.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API, Streaming Speech to Text API, Topic Extraction API, Sentiment Analysis API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-09-20 20:40 UTC

   We are currently investigating this issue.

2. investigating 2022-09-20 20:41 UTC

   We are continuing to investigate this issue.

3. identified 2022-09-20 21:55 UTC

   The issue has been identified and a fix is being implemented.

4. resolved 2022-09-21 01:18 UTC

   This incident has been resolved and users should no longer be experiencing increased response times from our APIs.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API, Streaming Speech to Text API, RTMP Ingestion, Custom Vocabulary API, Developer Dashboard, Topic Extraction API, Sentiment Analysis API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2022-08-16 20:16 UTC

   We are currently investigating this issue.

2. investigating 2022-08-16 20:23 UTC

   We are continuing to investigate this issue.

3. monitoring 2022-08-16 20:53 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2022-08-16 21:42 UTC

   We are continuing to monitor for any further issues. The Async API issues have resolved. We are seeing an improvement on the Streaming API, but users may experience an increase in streaming transcript turn around times.

5. monitoring 2022-08-16 22:51 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2022-08-16 23:50 UTC

   Keeping the issue open for now as we continue to monitor, but most users should no longer be experiencing increased Streaming Speech-To-Text Partial and Final latency. We do observe occasional slow response times from AWS S3 and we have escalated with our hosting provider.

7. resolved 2022-08-17 19:18 UTC

   This incident has been resolved. We are following up with our hosting providers to reduce the likelihood of this occurrence again.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2022-05-10 18:30 UTC

   This incident has been resolved. The issue spanned from 11:30 AM PT to 12 PM PT and affected a subset of our users, resulting in 5xx responses and failed API calls.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-01-13 22:44 UTC

   We are currently investigating this issue.

2. identified 2022-01-14 00:12 UTC

   This incident is being downgraded from partial outage to degraded performance. This partial degradation effects only non-english async transcription jobs. Users of non-english async transcription may observe an increase in turn around time. We have discovered that this incident...

3. monitoring 2022-01-14 00:48 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2022-01-14 03:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2022-01-10 15:00 UTC

   Between a 6:55am and 7:10am, some API requests from authentic users were rejected by the WAF due to a configuration change. The changes were rolled back immediately and a fix has been implemented. All traffic resumed normally after 7:10am 1/10/2022

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2021-12-15 15:30 UTC

   Our records indicate that there was an internet connectivity outage which lasted on our service from approximately 7:20am to 7:50am on December 15, 2021. AWS corroborates this with their own status messages. Because this was a partial internet connectivity outage, some requests...

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Asynchronous Speech to Text API, Streaming Speech to Text API, Custom Vocabulary API, On-Prem Licensing Server

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2021-04-01 20:12 UTC

   The issue effects job submission, custom vocabulary creation, on-premise licensing REST API endpoints in addition to the websocket streaming API. A fix has been implemented and we are monitoring the situation.

2. resolved 2021-04-01 20:13 UTC

   This incident has been resolved. The issue spanned from 10am PT to 11:30 PT

Excerpts are shortened. Read the full incident on Rev.ai's status page.

Affected: Streaming Speech to Text API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-12-07 23:22 UTC

   We are currently investigating the issue.

2. identified 2020-12-07 23:25 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2020-12-07 23:29 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2020-12-08 00:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rev.ai's status page.