Server-side streaming rejected new connections across all commercial regions

Final update

Server-side streaming began rejecting new connections across all commercial regions, causing 500/503 errors for customers attempting to establish new SDK streaming connections for a brief period of time. Detailed timelines of the incident: - us-east-1 : 7:53 AM PST to 8:24 AM PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.

1. Resolved · Mar 19, 16:58 UTC
   Server-side streaming began rejecting new connections across all commercial regions, causing 500/503 errors for customers attempting to establish new SDK streaming connections for a brief period of time. Detailed timelines of the incident: - us-east-1 : 7:53 AM PST to 8:24 AM PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.