Zingle incident
Messaging Outage (inbound/outbound) - Investigating
Zingle experienced a major incident on September 23, 2026 affecting app.zingle.me and Zings and 1 more component, lasting 4h 26m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 23, 2026, 10:21 AM UTC
We're investigating reports that login and outbound messages are not working for some Concierge services. Our team is actively investigating these issues and working to resolve them as soon as possible. We'll provide updates as they are available
- identified Sep 23, 2026, 10:55 AM UTC
We've identified the source and nature of the issue, and are continuing to work in order to resolve this as soon as possible. The issue was affecting login and outbound messaging traffic for a subset of Concierge phone numbers. We will continue to monitor this to ensure stability and provide updates accordingly.
- monitoring Sep 23, 2026, 02:21 PM UTC
We're investigating reports that login and outbound messages are not working for some Concierge services. Our team is actively investigating these issues and working to resolve them as soon as possible. We'll provide updates as they are available
- resolved Sep 23, 2026, 02:47 PM UTC
We confirmed that the issue reported earlier, where login and outbound messages were not working for some Concierge services has been resolved and users are no longer experiencing errors. No further action is needed from the users at this time.
- monitoring Sep 23, 2026, 02:55 PM UTC
We've identified the source and nature of the issue, and are continuing to work in order to resolve this as soon as possible. The issue was affecting login and outbound messaging traffic for a subset of Concierge phone numbers. We will continue to monitor this to ensure stability and provide updates accordingly.
- monitoring Sep 23, 2026, 06:47 PM UTC
We confirmed that the issue reported earlier, where login and outbound messages were not working for some Concierge services has been resolved and users are no longer experiencing errors. No further action is needed from the users at this time.