Errors sending outbound messages, updating conversations and importing contacts in Concierge App (app.zingle.me)

Incident
June 20, 2:57am

Errors sending outbound messages, updating conversations and importing contacts in Concierge App (app.zingle.me)

Status: closed
Start: June 19, 12:51pm
End: June 20, 2:57am
Duration: 14 hours 6 minutes
Affected Components:
app.zingle.me Web Inbox SMS Messaging Zings API Hospitality Integration System
Investigating

June 19, 12:51pm

June 19, 12:51pm

We have identified an issue impacting the Concierge App (app.zingle.me), where some users were unable to send outbound messages or reply to existing conversations. We're actively working on investigating and identifying the root cause of the issues. We'll continue to post updates here as needed, and appreciate your patience.

Investigating

June 19, 1:35pm

June 19, 1:35pm

We are continuing to work on identifying the source of the issues impacting the Concierge App in app.zingle.me. Users may see issues replying to conversations, sending outbound messages, making updates in the system or importing contacts. We have updates planned to mitigate these issues and impacted features. We'll continue to provide updates as they are available.

Investigating

June 19, 1:50pm

June 19, 1:50pm

We are continuing to investigate this issue.

Identified

June 19, 5:23pm

June 19, 5:23pm

Progress has been made in identifying the issues, and a fix is being tested to address them. We're continuing to work on mitigating the issues, and plan to have another update within the next hour. We appreciate your patience

Identified

June 19, 10:37pm

June 19, 10:37pm

We are continuing to work on addressing the issues impacting the Concierge App. The source of the issues have been identified, and updates are underway to restore the affected services. We'll continue to post updates as we have them and appreciate your patience.

Identified

June 20, 2:57am

June 20, 2:57am

We are continuing to work on a fix for this issue.

Resolved

June 20, 2:57am

June 20, 2:57am

This incident has been resolved.