Oyster Outage History
4 incidents recorded over the last 365 days, 4 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.
Every Recorded Oyster Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 15, 2026 | Intermittent page load issues for Cisco Umbrella usersWe have confirmed we've mitigated any conflicts with Cisco Umbrella. | 48h 55m | Resolved |
| Mar 16, 2026 | API Token Refresh degradedToken refresh working as expected | -4242 min | Resolved |
| Feb 2, 2026 | Transactional email (MFA included) unavailable.The issue upstream has been resolved and all of our transactional emails, including MFA codes, have been sent. | 1h 25m | Resolved |
| Nov 19, 2025 | High level of frontend errorsAll systems operating as expected. | 24 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Oyster incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Oyster 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 Oyster 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 Oyster outage in this window ran 2d, against a mean recovery of 16h 55m. If you depend on Oyster 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.