Stream API Outage History

19 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Stream API status99.75% uptime history

Every Recorded Stream API Incident

Stream API incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 5, 2026Data retrieval issue in US-EastThe incident has been resolved.4h 9mResolved
Jul 3, 2026Elevated API Errors in Singapore regionThe incident has been resolved.1h 30mResolved
Mar 12, 2026Elevated API Errors in US-EastThis incident has been resolved.43 minResolved
Mar 12, 2026Elevated API Errors in US-EastThis incident has been resolved.54 minResolved
Mar 11, 2026Maintenance to the storage layer in Singapore regionThe scheduled maintenance has been completed.3h 0mScheduled
Mar 11, 2026Maintenance to the storage layer in US-East regionThe scheduled maintenance has been completed.4h 0mScheduled
Mar 11, 2026Maintenance to the storage layer in Dublin regionThe scheduled maintenance has been completed.4h 0mScheduled
Mar 10, 2026Maintenance to the storage layer in Canada regionThe scheduled maintenance has been completed.4h 0mScheduled
Mar 10, 2026Maintenance to the storage layer in Ohio regionThe scheduled maintenance has been completed.4h 0mScheduled
Feb 11, 2026High error rate on Chat API service in dublinThis incident has been resolved.1h 21mResolved
Dec 2, 2025Elevated API Errors on Feed v3 and Chat in Ohio regionThis incident has been resolved.1h 17mResolved
Nov 11, 2025Send message failuresWe identified an issue with sending messages. The issue is resolved. We're looking into the root cause0 minResolved
Nov 5, 2025Maintenance to the storage layer in US-East regionThe scheduled maintenance has been completed.1h 30mScheduled
Nov 4, 2025Maintenance to the storage layer in Mumbai regionThe scheduled maintenance has been completed.1h 30mScheduled
Nov 4, 2025Maintenance to the storage layer in Ohio regionThe scheduled maintenance has been completed.1h 30mScheduled
Oct 21, 2025Mandatory upgrade to the storage layer in N.VirginiaThe scheduled maintenance has been completed.2h 0mScheduled
Oct 20, 2025Intermittent availability of the dashboardThis incident has been resolved.13h 20mResolved
Sep 23, 2025High error rate on Chat and Video API service in ohio regionThis incident has been resolved.9 minResolved
Sep 3, 2025High error rate on Chat and Feed API serviceThis incident has been resolved.9 minResolved

How to Read This Stream API Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Stream API acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Stream API outage in this window ran 13h 20m, against a mean recovery of 2h 35m. If you depend on Stream API in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.