AlertMedia Outage History

10 incidents recorded over the last 365 days, 10 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 AlertMedia Incident

AlertMedia incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Older Desktop Versions Failing to Sign InThis incident has been resolved and we are monitoring the situation.8h 32mResolved
Oct 23, 2026iOS mobile app closes on launch after latest updateThe new version of the mobile app is available in the Apple App Store for download.3h 1mResolved
Sep 1, 2026Communication SMS provider degraded (Twilio)This incident has been resolved.1h 45mResolved
Jun 4, 2026Mobile App login DegradationThis incident has been resolved.17h 14mResolved
Jun 3, 2026User Imports Failing UnexpectedlyThis incident has been resolved.6h 54mResolved
Jan 14, 2026Nationwide Verizon Outage (US)The outage is resolved, according to Verizon.8h 52mResolved
Jan 13, 2026We are investigating reports of intermittent latencyThis incident has been resolved1h 14mResolved
Dec 2, 2025AlertMedia Incident: Unable to loginThis incident has been resolved.29 minResolved
Nov 18, 2025Threat History & Safety MapsA fix has been implemented and we are monitoring the results. Both Threat History and Safety Maps are responsive.4h 38mResolved
Nov 14, 2025Investigating SFTP performance issuesThis incident has been resolved.6h 22mResolved

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 AlertMedia 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 AlertMedia 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 AlertMedia 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 AlertMedia outage in this window ran 17h 14m, against a mean recovery of 5h 54m. If you depend on AlertMedia 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.