Supercast Outage History
11 incidents recorded over the last 365 days, 10 of them resolved, 1 still open. 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 Supercast Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 29, 2026 | Delays in episode publicationWe've identified and repaired the issue and background queues are catching up. We'll continue to update as episodes are released. | — | Investigating |
| Aug 27, 2026 | Spotify issuesThis incident has been resolved. | 22h 3m | Resolved |
| Aug 5, 2026 | Delays in episode publishing, emails, and other functionalityAll jobs are now running within target. This issue is resolved. | 5 min | Resolved |
| Jul 24, 2026 | Intermittent outageFull connectivity restored. We did not have any clear issues with our application, this looks like it was an environmental issue external to Supercast. | 5 min | Resolved |
| Jun 1, 2026 | Issues playing audio episodes in subscriber areaThis issue is resolved | 14 min | Resolved |
| May 13, 2026 | Temporary delays in episode imports and new episode publicationThis incident has been resolved. | 12h 42m | Resolved |
| May 7, 2026 | Delays in episode publicationThis incident has been resolved. | 3h 17m | Resolved |
| Apr 29, 2026 | Scheduled Jobs outageWe've resolved this issue and all scheduled tasks should be running on schedule. During the period this status alert was running we were manually running critical jobs, but there was a period from late yesterday to… | 1h 34m | Resolved |
| Jan 8, 2026 | Episode & Post notification emails failing to sendThis incident has been resolved. | 1h 14m | Resolved |
| Jan 7, 2026 | Episode Publishing IssuesThis incident has been resolved. | 2681h 16m | Resolved |
| Nov 11, 2025 | Application slow downThis incident has been resolved. | 55 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 Supercast 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 Supercast 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 Supercast 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 Supercast outage in this window ran 111d 17h, against a mean recovery of 11d 8h. If you depend on Supercast 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.