MyCase - Public Outage History
5 incidents recorded over the last 365 days, 5 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 MyCase - Public Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 5, 2026 | Degraded Performance- Advanced SearchThis incident has been resolved. | 3h 53m | Resolved |
| Mar 23, 2026 | Partial Outage- Advanced Tier Search FunctionalityThis incident has been resolved. | 19h 37m | Resolved |
| Mar 20, 2026 | Partial Outage - Advanced Tier Search FunctionalityThis incident has been resolved. | 10h 39m | Resolved |
| Feb 11, 2026 | 502 ErrorsThis incident has been resolved. | 1h 34m | Resolved |
| Nov 19, 2025 | 500 ErrorsThis incident has been resolved. | 27 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 MyCase - Public 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 MyCase - Public 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 MyCase - Public 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 MyCase - Public outage in this window ran 19h 37m, against a mean recovery of 7h 14m. If you depend on MyCase - Public 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.