Site US3 - Degradation

Incident Report for Sinch

Resolved

This incident has been resolved.

Start Time: 2020-02-05 11:48 UTC
End Time: 2020-02-05 21:23 UTC
Posted Feb 05, 2020 - 22:08 UTC

Monitoring

Most of the connections to the US3 site are restored and per the previous update we are already routing traffic through our redundant connections.
We are continuing the work to fully restore all connections to US3 and we will continue to monitor closely.
Posted Feb 05, 2020 - 19:31 UTC

Update

While we are still working to fully resolve the network equipment issue on the US3 site. We would like to clarify that since 12:20 UTC our internal routing has been diverted away from the US3 site and traffic is stable. We still recommend all clients to use our redundant US2 site for the time being until further notice.
Posted Feb 05, 2020 - 16:05 UTC

Update

On-site technicians are still working on resolving this issue as quickly as possible, unfortunately we are unable to provide an updated ETA at this point. Clients are still advised to divert traffic to the redundant US2 site until the issue is resolved.
Posted Feb 05, 2020 - 14:30 UTC

Update

On-site technicians are still working on resolving this issue as quickly as possible, unfortunately we are unable to provide an updated ETA at this point. Clients are still advised to divert traffic to the redundant US2 site until the issue is resolved.
Posted Feb 05, 2020 - 13:46 UTC

Update

The issue has been identified as an issue with networking equipment at the site. ETA for fix is 45 minutes at this point. Clients are still advised to connect to the redundant US2 site for the time being.
Posted Feb 05, 2020 - 12:39 UTC

Identified

The issue has been identified and a fix is being implemented.
Posted Feb 05, 2020 - 12:33 UTC

Investigating

We are currently experiencing degradation on our US3 Site.
It is advised that clients connect to our redundant US2 site for the duration of this issue.
Please contact support if you have any questions.
Posted Feb 05, 2020 - 11:48 UTC
This incident affected: Messaging APIs (SMPP - US, HTTP - US), Verification (SMS Verification), and Lookup API Endpoints (ENUM US, HTTP US).