Loading
Applying language and content...
Loading status page
Checking service and reports...
50 Switchco incidents · март 2025 г. — official updates, affected components, duration and resolution details.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are continuing to investigate this issue.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating a potential outage for some customers.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some customers may be experiencing intermittent issues affecting various platform functions, including inbound/outbound calling, message delivery, and agent status synchronization. Our engineering team is actively working on a resolution. In the meantime, agents can manually update their status by clicking the 'Refresh' button within the application.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue is due to a worldwide CloudFlare service incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. Users can go directly to https://dialpad.com/login to sign in. Calling and messaging are unaffected.
A fix has been implemented and we are monitoring the results.
The service is fully recovered.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are currently investigating this issue.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue is identified and we are working on a fix. If you are affected, please try this potential workaround: 1) Disable post-call wrap-up: https://help.dialpad.com/docs/post-call-wrap-up-time#enable-postcall-wrapup-time 2) A contact center supervisor should select the relevant contact center in the app and manually set each affected agents' status to Available
A mitigation has been applied and operator status will be recovering over time. We will provide an update when fully recovered.
Our mitigation has completed and operator status has recovered. We will continue to monitor.
This incident has been resolved.
We are currently investigating this issue.
The incident appears to have started at 16:30 UTC (9:30am Pacific) and ended 3 minutes later. We are investigating.
We have not seen recurrence of the issue, but are continuing to investigate the root cause.
We have identified the issue and have not seen recurrence. We will continue to monitor and root cause.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We believe the issue occurred earlier in the day with a certain numbers and was resolved by 18:00 UTC. We are continuing to investigate the underlying cause with our carrier partner.
This incident has been resolved.