Mobile Messaging
Since approximately 21:33 UTC, we are investigating an issue involving the API component. Our engineering team is working to resolve the issue. We will update our status page with additional affected components (if necessary) as soon as we have more information.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
We have resolved the issue impacting sends. We are continuing to monitor.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com, you have any questions or concerns.
Since 04:00 AM UTC, an issue involving messages targeting attributes and custom events on the EU Cloud occurred.
Communications using other targeting channels are working as expected.
Our engineering team is actively engaged and working to identify the root cause to resolve the latency as quickly as possible.
We will provide another update as soon as more information becomes available.
If you have any questions, please contact Technical Support at https://support.airship.com.
Our engineering team is currently reviewing the latency that is now resolving within our system.
We will provide another update as soon as we have more information.
If you have any questions or concerns, please contract Technical Support at https://support.airship.com.
This issue has been resolved and services have been fully restored.
Please feel free to reach out to Airship Technical Support if you have any questions or concerns https://support.airship.com.
Since 12:00 UTC, we have been investigating an issue that is resulting in delays for pushes sent using our mixed segmentation (tags and attributes) feature. Pushes without segmentation are unaffected by this delay and performing normally.
Our engineering team is working to identify and resolve this matter.
We will update our status page as soon as we have more information.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Our engineering team has found the source of the issue. We are currently monitoring the system.
This incident has been resolved.
Scheduled Change: Airship is in the process of migrating all TLS (Transport Layer Security) certificates from DigiCert to Google Trust Services (GTS). This is a phased rollout across our global infrastructure to ensure continued compliance with modern security standards.
Timeline & Impacted Endpoints:
- General Migration: Rollout for various supplemental and regional endpoints is currently underway and may be completed ahead of the primary domains.
- Primary Domains: Migration for the following key endpoints is scheduled to begin on June 1, 2026:
- Dashboard: go.airship.com
- API Endpoints: go.urbanairship.com, go.asnapieu.com
Action Required: If your systems rely on standard root certificate stores (the default for most modern browsers and servers), no action is required. However, if your engineering team has "pinned" or hardcoded DigiCert Root or Intermediate certificates, your connection to Airship will fail upon migration. To prevent service disruption, we strongly recommend removing these pins immediately.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Since 06:15 UTC, we are currently investigating an issue that is resulting in an increased rate of 5xx errors when sending push notifications from the API and the Go Dashboard.
Our engineering team is working to identify and resolve this point. We will update our status page as soon as we have more information.
Please feel free to contact Airship Technical Support at https://support.airship.com, you have any questions or concerns.
We have deployed corrective actions, and our systems are returning to normal. We are currently monitoring the system.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Since 15:54 UTC we are investigating an issue involving the Mobile Messaging component. Our engineering team is working to resolve the issue. We will update our status page with additional affected components (if necessary) as soon as we have more information.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Since 15:32 UTC we are investigating an issue involving the Mobile Messaging component. Customers sending messages with segmentations may encounter delays regarding the delivery of the messages. Our engineering team as identified the source of the behavior and is working to resolve the issue.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Our engineering team has found the source of the issue. We are currently monitoring the system.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Since 10.48 AM UTC, we are investigating an issue that is resulting in delays in messages using segmentation.
Our engineering team is working to resolve this issue.
We will update our status page as soon as we have more information.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Our engineering team has found the source of the issue. We are currently monitoring the system.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Since 12:23 UTC we've identified an issue involving messages using segmentation. This may have generated delays of some campaigns that have been sent since July 27.
Our engineering team has implemented a fix, but they are still investigating the root cause.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
Our engineering team has found the source of the issue. We are currently monitoring the system.
Please, feel free to contact Airship Technical Support at https://support.airship.com, if you have any questions or concerns.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
As of 08:10 AM UTC, we are investigating an issue involving message segmentation. Our engineering team have implemented a fix as of 09:15 UTC, and they are monitoring the issue. Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
We are investigating an issue involving the APNS Push Notification component that started around 20:47 UTC. Our engineering team is working to resolve the issue. We will update our status page with additional affected components as soon as we have more information. Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.
We have deployed a fix to the APNS delivery component, and performance is back to normal. Our system is still processing messages in our backlog. We will continue to monitor the incident.
This incident has been resolved.
Please feel free to contact Airship Technical Support at https://support.airship.com if you have any questions or concerns.