Ιστορικό διακοπών του Stream

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

We're experiencing an elevated level of API errors and are currently looking into the issue.

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

This incident has been resolved.

We're experiencing an elevated level of API errors and our team is currently working on a mitigation.

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

This incident has been resolved.

We're experiencing an elevated level of API errors and are currently looking into the issue.

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

This incident has been resolved.

We identified an issue with sending messages. The issue is resolved. We're looking into the root cause

We're currently investigating an issue with Stream's dashboard. The issue is caused by an outage of AWS.

This incident has been resolved.

One of our shards in the ohio region is experiencing an issue with the underlying database storage. Our team is actively working to restore the service.

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

This incident has been resolved.

We experienced a brief service degradation in some shards in the US-East region. The issue lasted for 1 minute and has since been resolved. Our team is currently monitoring the situation.

This incident has been resolved.

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

This incident has been resolved.

There was a significant spike in requests that hit one of our Edge shards in the US-East region, leading to an exhaustion of resources. The incident lasted 4 minutes.

One of our shards in the us-east region is experiencing an issue with the underlying database storage. Our team is actively working to restore the service.

The issue is being resolved, and our team is closely monitoring the database.

This incident has been resolved.

Between 12:35 and 12:51 UTC, our API layer experienced a downtime in the Mumbai region due to increased system load. We are currently investigating the incident and implementing a patch. During this time API requests to join calls returned a 5xx response.

Our team deployed a patch to the affected system and the incident has been resolved

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

One of our shards in the US-East region is experiencing degraded performance due to an issue with the underlying data storage. Our team is currently working on resolving the incident.

This incident has been resolved.

One of our shards in the Dublin region is experiencing degraded performance due to an issue with the underlying data storage. Our team is currently working on resolving the incident.

The incident has been resolved.

APIs are partially unreachable for users within the UAE on the DU Telecom and Virgin Telecom ISPs. Our team is currently working to remediate the problem by talking to the ISP and local authorities, a temporary remediation is also in progress.

This incident has been resolved.

Our monitoring system has detected an incident affecting one of our shard in Ohio. Customers located on that shard have experienced a high error rate.

The incident has been resolved, and traffic is now served without any issue.

We are currently experiencing a high error rate on one of our Feed shards in the us-east region. Our team is actively working to resolve the situation.

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

The shard has been recovered and the incident has been resolved. Our team is currently conducting an internal investigation to determine the root cause of the issue.

At 21:02 CET, a high error rate was recorded on the Chat API endpoints in one of our us-east shards. Our team resolved the issue at 21:18 CET, and the service is now operating normally.

An issue with the QueryChannel endpoint led to some queries returning HTTP 403 response code. This incident has been resolved.

We are currently investigating an issue with our Feed Realtime service.

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

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

This incident has been resolved.