Airship Outage History

Airship experienced an issue with their Mobile Messaging component starting at 10:15 AM PST that lasted 10.7 hours. The engineering team identified the source of the problem and the system recovered by 12:41 PM PST the same day. The incident was classified as minor and the team continued monitoring to ensure no additional issues occurred.

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.

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.

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.