An "not found"-error is causing telephony issues for some customers

Resolved
Resolved

Since last recovery update our services has been stable and fully operational – We are resolving this incident status.

We apologize for the inconvenience and appreciate your understanding.

Recovering

We've are seeing improvements in the service which has started to recover – we will continue to monitor the situation.

Updated

We are still working to resolve the issue for affected customers.

Our apologies for the inconvenience. Restoring the service as quickly as possible remains our top priority.

We will keep you updated.

Identified

We've confirmed there is a problem, we're working to resolve it.

Investigating

We are currently investigating reports of ongoing service interruptions.

We apologise for any inconvenience and will post another update as soon as we learn more.

Began at:

Affected components
  • App
    • Calendar Integrations
    • Journeys
    • Web Application (HTTPS)
    • Warehouse
    • File Upload
    • Analytics
    • Dialer
    • Number Store (DIDs)
    • Support Chat
  • Telephony
    • Call Recordings
    • Outbound
    • Inbound
  • SMS
    • Inbound
    • Outbound