Megaphone Outage History

23 incidents recorded over the last 365 days, 23 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 Megaphone status100.00% uptime history

Every Recorded Megaphone Incident

Megaphone incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 2, 2026Delayed downloads dataThis incident has been resolved.24h 44mResolved
Sep 29, 2026Account linking and data query issueThe incident has been resolved.4h 3mResolved
Sep 23, 2026Episode uploading issueThis incident has been resolved.2h 6mResolved
Sep 21, 2026Issues with episode managementThe incident has been resolved.1h 7mResolved
Sep 3, 2026Order updates not saving correctlyThis incident has been resolved.19 minResolved
Aug 7, 2026Intermittent issue with episode publishing on SpotifyThis incident has been resolved.1h 57mResolved
Aug 5, 2026Partial outage impacting Spotify loginThis incident has been resolved.2h 36mResolved
Jul 21, 2026Delayed episode processingThe incident has been resolved.21h 34mResolved
Jun 26, 2026Spotify Login not workingSpotify Login should now be functioning as expected.20 minResolved
Jun 24, 2026Delayed video podcast processingThe incident has been resolved.17h 11mResolved
Jun 5, 2026Delay in Spotify Partner Program estimated earnings reportingThis incident has been resolved.72h 56mResolved
May 29, 2026Intermittent 500 errors in CMSThe incident has been resolved.2h 28mResolved
May 15, 2026Episode processing and publishing issuesThis incident has been resolved.4h 0mResolved
May 6, 2026Timeouts and slow performance on Megaphone CMSThe incident is now resolved. Episodes that were stuck in processing have been resubmitted.4h 29mResolved
Apr 23, 2026Transcoding delaysThe incident has been resolved.4h 26mResolved
Apr 22, 2026Processing issueThe incident has been resolved.13h 49mResolved
Apr 21, 2026Audio upload issuesThe team identified an issue with episode uploads. The problem should now be resolved. Please try again if you were encountering issues previously.-3 minResolved
Apr 1, 2026Episodes stuck in processingThe incident has been resolved.5h 10mResolved
Feb 24, 2026Processing failure issuesThe processing issue has been resolved.17h 10mResolved
Jan 30, 2026Intermittent 504 timeout errorsThe maintenance update is complete.2h 30mResolved
Jan 28, 2026Megaphone CMS 504 errorsThis incident has been resolved.5h 7mResolved
Jan 9, 2026Chat Support Outage- IntercomIntercom has restored its service, and chat support is operational.24h 45mResolved
Nov 18, 2025Episode processing failuresThis incident has been resolved and impacted episodes have been reprocessed.3h 20mResolved

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 Megaphone 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 Megaphone 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 Megaphone 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 Megaphone outage in this window ran 3d, against a mean recovery of 10h 44m. If you depend on Megaphone 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.