Simplecast Outage History
7 incidents recorded over the last 365 days, 6 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 Simplecast Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 21, 2026 | Episode Audio File upload delayWe've experienced a delay on the audio file upload process for episodes in the past few hours. The backend is now stable and operational. | 0 min | Resolved |
| Jul 31, 2026 | Scheduled maintenance - Audience mapsThe scheduled maintenance has been completed. | 72h 0m | Scheduled |
| Jul 6, 2026 | Content - Audience - Web Player stats reporting issueThe reporting issue has been addressed. | 2h 14m | Resolved |
| May 21, 2026 | Simplecast Professional - Monetization Tab Data Display IssueWe can confirm that the service has fully recovered and that the platform is operating normally. | 10 min | Resolved |
| May 18, 2026 | Ad Delivery issueWe experienced an issue affecting ad insertion and delivery between May 15 at 14:00 UTC and May 16 at 23:00 UTC. During this time, an incorrect targeting rule in the backend prevented ads from being eligible for… | -4681 min | Resolved |
| May 11, 2026 | RSS Show NameIssue has been resolved. All impacted RSS feeds should be shortly updated (this time may vary depending on each player's behavior). | 13 min | Resolved |
| Jan 30, 2026 | UI Analytics graphs reporting issueThis incident has been resolved. | 63h 14m | 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 Simplecast 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 Simplecast 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 Simplecast 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 Simplecast outage in this window ran 3d, against a mean recovery of 22h 59m. If you depend on Simplecast 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.