Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Switchco outage history

    60 recorded Switchco incidents since March 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Some customers may be experiencing issues with devices.

    Started October 20, 2026 at 3:49 PM UTC · 6h 5m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. October 20, 2026 at 3:49 PM UTCinvestigating

      We believe the issue is primarily impacting customers whose networks have trouble with large DNS records or those using Grandstream ATA devices. Our team is working on a resolution. We will update when it is resolved.

    2. October 20, 2026 at 4:38 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. October 20, 2026 at 8:22 PM UTCmonitoring

      We've resolved issues for most customers by now.

    4. October 20, 2026 at 9:54 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing issues making or receiving calls.

    Started October 20, 2026 at 1:44 AM UTC · 7h 37m

    OutageMajor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. October 20, 2026 at 1:44 AM UTCinvestigating

      We are investigating a potential outage for some customers.

    2. October 20, 2026 at 2:18 AM UTCinvestigating

      We are continuing to investigate the issue. Next update in 30 minutes.

    3. October 20, 2026 at 3:16 AM UTCinvestigating

      We are continuing to investigate this issue. Our engineering team is actively working on a resolution. Next update within 30 minutes.

    4. October 20, 2026 at 3:46 AM UTCinvestigating

      Our engineering team is currently testing a potential fix. We will provide an update within the next 30 minutes.

    5. October 20, 2026 at 4:16 AM UTCinvestigating

      We are continuing to test the fix. Next update within 30 minutes.

    6. October 20, 2026 at 4:54 AM UTCidentified

      The issue has been identified and service is starting to recover with the fix. We are currently working on full recovery. Next update in 30 minutes.

    7. October 20, 2026 at 7:28 AM UTCinvestigating

      Customers are still experiencing issues on some types of devices and the engineering team is continuing their investigation.

    8. October 20, 2026 at 8:57 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    9. October 20, 2026 at 9:21 AM UTCresolved

      This incident has been resolved.

    Service degradation affecting some IVR Customers

    Started September 23, 2026 at 5:20 PM UTC · 45m

    IssuesMinor incident
    Affected components
    Omnichannel
    1. September 23, 2026 at 5:20 PM UTCmonitoring

      Service degradation affecting some IVR Customers

    2. September 23, 2026 at 6:06 PM UTCresolved

      This incident has been resolved.

    Some users with US toll-free or midwest toll numbers may have had trouble with new or ongoing calls

    Started September 15, 2026 at 4:08 PM UTC · 19m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. September 15, 2026 at 4:08 PM UTCmonitoring

      Network issue in the midwest US impacted some new and existing calls in the region. The incident lasted approximately 6 minutes and traffic has been successfully rerouted.

    2. September 15, 2026 at 4:09 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    3. September 15, 2026 at 4:27 PM UTCresolved

      This incident has been resolved.

    Investigating degraded calling performance for some EU numbers and destinations

    Started September 3, 2026 at 9:54 AM UTC · 42m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsCarrier Networks: Local NumbersApplicationTelephony Infrastructure: Outbound Calls
    1. September 3, 2026 at 9:54 AM UTCinvestigating

      We are currently investigating this issue.

    2. September 3, 2026 at 10:12 AM UTCinvestigating

      We are continuing to investigate this issue.

    3. September 3, 2026 at 10:19 AM UTCidentified

      The issue has been identified with a telephony carrier. Outbound calling has been routed around the problematic carrier, but inbound calls could still be impacted.

    4. September 3, 2026 at 10:27 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    5. September 3, 2026 at 10:36 AM UTCresolved

      This incident has been resolved.

    Partial service disruption

    Started September 1, 2026 at 3:25 PM UTC · 4h 37m

    OutageMajor incident
    Affected components
    Telephony Infrastructure: Inbound Calls
    1. September 1, 2026 at 4:05 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    2. September 1, 2026 at 4:44 PM UTCinvestigating

      We are currently investigating this issue.

    3. September 1, 2026 at 5:14 PM UTCinvestigating

      We are continuing to investigate this issue.

    4. September 1, 2026 at 6:34 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    5. September 1, 2026 at 6:35 PM UTCidentified

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

    6. September 1, 2026 at 7:03 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    7. September 1, 2026 at 8:02 PM UTCresolved

      This incident has been resolved.

    Some contact center agents may be experiencing issues with being unable to complete a call wrap-up

    Started August 21, 2026 at 4:21 PM UTC · 49m

    IssuesMinor incident
    Affected components
    Contact Center
    1. August 21, 2026 at 4:21 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    2. August 21, 2026 at 4:42 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results. Agents should refresh their application to pick up the change.

    3. August 21, 2026 at 5:09 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing errors using the fax API

    Started July 28, 2026 at 4:22 PM UTC · 28m

    IssuesMinor incident
    Affected components
    API Platform
    1. July 28, 2026 at 4:22 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    2. July 28, 2026 at 4:50 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing degraded performance with IVR calls

    Started July 7, 2026 at 6:38 PM UTC · 1h 24m

    IssuesMinor incident
    Affected components
    Contact Center
    1. July 7, 2026 at 6:38 PM UTCinvestigating

      Some customers may be experiencing degraded performance with IVR calls. The degraded calls will be going to designated fallbacks.

    2. July 7, 2026 at 7:26 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. July 7, 2026 at 7:33 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. July 7, 2026 at 8:02 PM UTCresolved

      This incident has been resolved.

    Inbound/Outbound Calling Potentially Impacted

    Started June 30, 2026 at 11:23 PM UTC · 6h 16m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. June 30, 2026 at 11:23 PM UTCinvestigating

      We are investigating a potential impairment with calling.

    2. June 30, 2026 at 11:54 PM UTCmonitoring

      A fix has been applied. Calling operations returned to normal.

    3. July 1, 2026 at 5:38 AM UTCresolved

      This incident has been resolved.

    Some customers in the US and Canada may be experience issues with delays in message delivery

    Started June 11, 2026 at 8:55 PM UTC · 2h 47m

    IssuesMinor incident
    Affected components
    Carrier Networks: Messaging
    1. June 11, 2026 at 8:55 PM UTCinvestigating

      We are currently investigating this issue.

    2. June 11, 2026 at 9:01 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. June 11, 2026 at 9:40 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. June 11, 2026 at 11:42 PM UTCresolved

      This incident has been resolved.

    Some customers in the US and Canada may be experiencing issues with MMS messaging

    Started June 9, 2026 at 4:34 PM UTC · 40m

    OutageMajor incident
    Affected components
    Messaging
    1. June 9, 2026 at 4:34 PM UTCinvestigating

      We are currently investigating this issue.

    2. June 9, 2026 at 5:03 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. June 9, 2026 at 5:14 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing issues receiving inbound SMS messages

    Started June 8, 2026 at 10:43 PM UTC · 3h 10m

    IssuesMinor incident
    Affected components
    Messaging
    1. June 8, 2026 at 10:43 PM UTCinvestigating

      We are currently investigating the issue.

    2. June 9, 2026 at 1:02 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. June 9, 2026 at 1:53 AM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing issues with IVR

    Started May 20, 2026 at 6:58 PM UTC · 5h 29m

    OutageMajor incident
    Affected components
    Omnichannel
    1. May 20, 2026 at 7:36 PM UTCinvestigating

      We are continuing to investigate this issue.

    2. May 20, 2026 at 10:18 PM UTCinvestigating

      We are currently investigating this issue.

    3. May 20, 2026 at 11:33 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    4. May 20, 2026 at 11:55 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    5. May 21, 2026 at 12:26 AM UTCresolved

      This incident has been resolved.

    Customers using Salesforce CTI with Dialpad may be experiencing issues with logging in

    Started May 4, 2026 at 3:11 PM UTC · 3h 6m

    IssuesMinor incident
    Affected components
    Integrations
    1. May 4, 2026 at 3:11 PM UTCinvestigating

      We are currently investigating this issue.

    2. May 4, 2026 at 3:19 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. May 4, 2026 at 5:29 PM UTCidentified

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

    4. May 4, 2026 at 5:39 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    5. May 4, 2026 at 6:17 PM UTCresolved

      This incident has been resolved.

    We are investigating potential issues with calling

    Started April 8, 2026 at 7:17 PM UTC · 2h 1m

    OutageMajor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. April 8, 2026 at 7:17 PM UTCinvestigating

      We are currently investigating this issue.

    2. April 8, 2026 at 7:44 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 8, 2026 at 9:18 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing issues making or receiving calls.

    Started March 10, 2026 at 3:47 PM UTC · 2d 6h

    IssuesMinor incident
    Affected components
    MessagingApplicationAnalyticsTelephony Infrastructure: Outbound CallsOmnichannel
    1. March 10, 2026 at 3:47 PM UTCinvestigating

      We are investigating a potential outage for some customers.

    2. March 10, 2026 at 5:29 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. March 10, 2026 at 5:31 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. March 12, 2026 at 10:11 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing sporadic issues with placing or receiving calls

    Started February 13, 2026 at 4:39 PM UTC · 52m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. February 13, 2026 at 4:39 PM UTCinvestigating

      We are currently investigating this issue.

    2. February 13, 2026 at 4:46 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. February 13, 2026 at 5:31 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing sporadic issues with placing or receiving calls

    Started February 12, 2026 at 2:47 PM UTC · 1h 4m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
    1. February 12, 2026 at 2:47 PM UTCinvestigating

      We are currently investigating this issue.

    2. February 12, 2026 at 2:56 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. February 12, 2026 at 3:52 PM UTCresolved

      This incident has been resolved.

    Some customers may be experiencing delays in platform functions

    Started January 13, 2026 at 5:37 PM UTC · 3h 2m

    IssuesMinor incident
    Affected components
    Telephony Infrastructure: Inbound CallsAPI PlatformMessagingGoogle Cloud PlatformApplicationContact CenterOmnichannel
    1. January 13, 2026 at 5:37 PM UTCinvestigating

      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.

    2. January 13, 2026 at 5:52 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. January 13, 2026 at 5:58 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. January 13, 2026 at 8:38 PM UTCresolved

      This incident has been resolved.