Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Airship Outage History

Every past Airship outage tracked by IsDown, with detection times, duration, and resolution details.

There were 146 Airship outages since November 2018. The 21 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 5, 2026

May 2026: Investigating an issue with the Mobile Messaging component

Detected May 5, 2026 6:14 AM EDT · Resolved May 5, 2026 11:44 PM EDT · Duration about 18 hours

Airship experienced a service degradation affecting Mobile Messaging, Web Notifications, Email Messaging, and SMS Messaging components, causing delivery delays for non-broadcast messages and issues with features relying on attributes, personalization, and mixed segmentation. The engineering team identified and resolved the primary issue after several hours, though some customers continued to experience delays with personalized messaging features. The incident lasted 17.5 hours with full service restoration completed by the engineering team.

Minor March 10, 2026

March 2026: Investigating an issue with the APIs component

Detected Mar 10, 2026 11:46 PM EDT · Resolved Mar 11, 2026 7:27 AM EDT · Duration about 8 hours

Airship experienced increased 5xx errors affecting both public APIs and Go Dashboard internal APIs from 01:02am to 3:18am PST. The engineering team successfully mitigated and resolved the issue after approximately 2 hours and 16 minutes of investigation. The system is now being monitored following the resolution.

Minor March 3, 2026

March 2026: Issues with evaluating tags, events, and attributes

Detected Mar 3, 2026 2:32 AM EST · Resolved Mar 3, 2026 11:02 AM EST · Duration about 9 hours

Airship experienced delays in message deliveries that used tags, events, or attributes for segmentation, affecting APIs, Mobile Messaging, Web Notifications, and Email Messaging for 8.5 hours. Messages without segmentation criteria continued to function normally during the incident. The engineering team identified the root cause, processed the backlog of delayed messages, and restored normal service while monitoring for full recovery.