Rev AI

This incident has been resolved.

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 the root cause and a fix is in progress

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

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.

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

We are continuing to monitor for any further issues.

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

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

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 hypothesis delayed by up to a minute during the event. If users are following our guidance and buffering audio locally and attempting to reconnect to the server when a server side termination is initiated, impact to end users would have been minimal. We are continuing to investigate the underlying cause to prevent any future disruptions such as these.

We are continuing to investigate this issue.

We are currently investigating this issue.

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.

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

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

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

This incident has been resolved.

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

We are currently investigating this issue.

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

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

We are continuing to investigate this issue.

We are currently investigating this issue.

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

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.

We are continuing to monitor for any further issues.

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.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

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.

This incident has been resolved.

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

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 has not resulted in any job failures. We have identified the issue is linked to one of our web infrastructure service providers. We are continuing to work on a fix.

We are currently investigating this issue.

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

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 continued to resolve during this period. From AWS Service health page on December 15 2021: 7:43 AM PST We are investigating Internet connectivity issues to the US-WEST-2 Region. 8:01 AM PST We have identified the root cause of the Internet connectivity to the US-WEST-2 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery. 8:14 AM PST We have resolved the issue affecting Internet connectivity to the US-WEST-2 Region. Connectivity within the region was not affected by this event. The issue has been resolved and the service is operating normally. 12:14 PM PST Between 7:14 AM PST and 7:59 AM PST, customers experienced elevated network packet loss that impacted connectivity to a subset of Internet destinations. Traffic within AWS Regions, between AWS Regions, and to other destinations on the Internet was not impacted. The issue was caused by network congestion between parts of the AWS Backbone and a subset of Internet Service Providers, which was triggered by AWS traffic engineering, executed in response to congestion outside of our network. This traffic engineering incorrectly moved more traffic than expected to parts of the AWS Backbone that affected connectivity to a subset of Internet destinations. The issue has been resolved, and we do not expect a recurrence.

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

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.

This incident has been resolved.

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

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

We are currently investigating the issue.