2600Hz Outage History

2600Hz is up right now

Pingoru has recorded 50 incidents for 2600Hz: 7 in the last 12 months and 2 in the last 90 days.

Source: status.2600hz.com

50incidents recorded
7last 12 months
2last 90 days
8 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking 2600Hz in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202622 of 744 (0%)
August 202612 of 744 (0%)
September 202600 of 720 (0%)
October 2026110 of 508 (2%)

Incidents, newest first

Minor October 21, 2026 Temporary Unavailability of Provisioner and Support Portal 10h 21m Support Portal, Advanced Provisioner

Started Oct 21, 2026, 01:44 PM UTC· resolved Oct 22, 2026, 12:05 AM UTC

  1. identified Oct 21, 2026, 01:44 PM UTC

    Out of an abundance of caution due to ongoing external factors, we have temporarily disabled the Provisioner while our team puts an update in place. During this time, customer access to the Support Portal is also unavailable. All other services continue to operate normally. While the portals are unavailable, you can still reach our Support team: Email: Send your request to [email protected] and a ticket will be opened for you. Phone: For urgent issues, our support line is accepting inbound calls as usual at 415-886-7950. We apologize for the inconvenience and will post an update here as soon as access is restored. Thank you for your patience.

  2. identified Oct 21, 2026, 02:51 PM UTC

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

  3. identified Oct 21, 2026, 03:27 PM UTC

    Please be advised, TTS servers are also impacted. Though we believe we have mitigated this without impact to clients. If you experience any problems generating new TTS, please contact our support team.

  4. monitoring Oct 21, 2026, 07:10 PM UTC

    Provisioner is operational and continues to be monitored for stability. The Support Portal will remain available via email only. Cluster Manager (CM) will remain unavailable at this time. We will provide additional updates as needed.

  5. monitoring Oct 21, 2026, 08:40 PM UTC

    We are currently working on restoring Cluster Manager. As part of this work, the IP addresses associated with Cluster Manager will be changing. Customers with firewall rules or IP allowlists may need to update their configurations. We will provide the new IP addresses once they are available. We will continue to provide updates as work progresses.

  6. resolved Oct 22, 2026, 12:05 AM UTC

    Cluster Manager (CM) is now back up and fully functional. If you would like new IP addresses, please email [email protected]. Aside from the Support Portal web interface, all services are operating normally. Our team is continuing to work on restoring the web interface, and we will post an update as soon as it is available. In the meantime, Support remains reachable by email at [email protected] or by phone at 415-886-7950. Thank you for your patience.

Read the full incident report →

Minor August 17, 2026 Provisioning issue - Yealink Phones 2h 11m Advanced Provisioner

Started Aug 17, 2026, 03:58 PM UTC· resolved Aug 17, 2026, 06:09 PM UTC

  1. identified Aug 17, 2026, 03:58 PM UTC

    We are seeing reports of issues when attempting to provision Yealink phones. We have identified the root cause and are working to implement a fix.

  2. identified Aug 17, 2026, 03:58 PM UTC

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

  3. resolved Aug 17, 2026, 06:09 PM UTC

    A fix has been implemented, and the issue is now fixed. We will continue to monitor.

Read the full incident report →

Minor July 15, 2026 API Issues on Hosted 25m Management Portal

Started Jul 15, 2026, 06:40 PM UTC· resolved Jul 15, 2026, 07:05 PM UTC

  1. investigating Jul 15, 2026, 06:40 PM UTC

    We are investigating potential API issues on the ZSwitch US system in the SJC zone.

  2. investigating Jul 15, 2026, 06:41 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 15, 2026, 06:47 PM UTC

    We have identified the issue and are working on resolving the issue.

  4. monitoring Jul 15, 2026, 06:57 PM UTC

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

  5. resolved Jul 15, 2026, 07:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 12, 2026 Connectivity Alerts 07/12/26 1h 27m Telephony Services

Started Jul 12, 2026, 09:51 PM UTC· resolved Jul 12, 2026, 11:19 PM UTC

  1. investigating Jul 12, 2026, 09:51 PM UTC

    We're currently seeing heightened alerts related to connectivity between zones, we're engaging our infrastructure team to investigate further. We'll update here as soon as we know more, in the meantime please raise a ticket with us if you're experiencing any degradation to service.

  2. resolved Jul 12, 2026, 11:19 PM UTC

    The issues we saw should now be resolved; this was limited to hosts in the SJC zone. We will send out a full RCA in due course, please let us know if you experience any further issues.

Read the full incident report →

Notice February 20, 2026 Investigating reports of outages 1h 24m Telephony Services, Management Portal, Advanced Provisioner, Cluster Manager

Started Feb 20, 2026, 06:09 PM UTC· resolved Feb 20, 2026, 07:33 PM UTC

  1. investigating Feb 20, 2026, 06:09 PM UTC

    We are currently investigating Zabbix alerts/reports of outages affecting portal/calls. We will send out an update as ASAP.

  2. investigating Feb 20, 2026, 06:15 PM UTC

    This appears to a problem with Level3 currently; our infrastructure team is investigating implementing routing changes to workaround the issue.

  3. investigating Feb 20, 2026, 06:35 PM UTC

    Cloudflare appears to have stopped advertising our 8.X addresses causing this outage; we have now re-enabled them. We're working with CloudFlare to investigate the root cause but are seeing issues resolve from our side.

  4. resolved Feb 20, 2026, 07:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 27, 2026 Degraded performance in ORD zone due to Cloudflare issues 20h 57m Telephony Services

Started Jan 27, 2026, 08:26 PM UTC· resolved Jan 28, 2026, 05:23 PM UTC

  1. identified Jan 27, 2026, 08:26 PM UTC

    We are seeing degraded performance and intermittent issues in the ORD zone due to a Cloudflare issue: https://www.cloudflarestatus.com/ We are monitoring the situation. Users who are experiencing issues can route away from the ORD zone by cutting over to the east or west zones.

  2. monitoring Jan 28, 2026, 12:13 AM UTC

    Cloudflare has reported a fix has been implemented. We are monitoring for issues.

  3. resolved Jan 28, 2026, 05:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 13, 2025 ZSwitch partial outage 21h 37m Telephony Services, Management Portal, Advanced Provisioner, Cluster Manager

Started Nov 13, 2025, 08:08 PM UTC· resolved Nov 14, 2025, 05:46 PM UTC

  1. investigating Nov 13, 2025, 08:08 PM UTC

    We are investigating an issue with a partial outage due to loss of connectivity to one of our zones.

  2. investigating Nov 13, 2025, 08:14 PM UTC

    We are experiencing uptime issues with our San Jose datacenter and are working to resolve it. Phones that are properly configured to register to SRV/NAPTR records should fail over to the other zones.

  3. investigating Nov 13, 2025, 08:28 PM UTC

    We are seeing a fiber related issue in our San Jose datacenter and are working to resolve it.

  4. monitoring Nov 13, 2025, 08:39 PM UTC

    We have resolved the issue and believe we are operational at this time. We are monitoring the incident.

  5. resolved Nov 14, 2025, 05:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 2, 2025 ZSwitch SMS Issues 2h 5m Telephony Services

Started Sep 02, 2025, 05:11 PM UTC· resolved Sep 02, 2025, 07:16 PM UTC

  1. investigating Sep 02, 2025, 05:11 PM UTC

    We've observed issues with Inbound/Outbound SMS and MMS and have confirmed this appears to be consistently impacting all of ZSwitch.

  2. resolved Sep 02, 2025, 07:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 20, 2025 Zswitch US outage. 11h 11m Telephony Services

Started Aug 20, 2025, 10:50 AM UTC· resolved Aug 20, 2025, 10:01 PM UTC

  1. investigating Aug 20, 2025, 10:50 AM UTC

    We are currently investigating an issue with Zswitch US' database services. We have engaged our engineering and operations team to work this as highest priority. We will update this page as soon as we know more.

  2. investigating Aug 20, 2025, 12:32 PM UTC

    This issue has now been resolved and the database services are operating as expected. We are working on a full RCA and will update this statuspage with it in due course. If you have any questions in the meantime please contact support using the normal methods.

  3. monitoring Aug 20, 2025, 12:32 PM UTC

    This issue has now been resolved and the database services are operating as expected. We are working on a full RCA and will update this statuspage with it in due course. If you have any questions in the meantime please contact support using the normal methods. We will continue to monitor throughout the day.

  4. monitoring Aug 20, 2025, 07:23 PM UTC

    We are seeing further degradation in the system and are investigating

  5. monitoring Aug 20, 2025, 07:30 PM UTC

    We've stabilized services and are continuing to monitor the situation.

  6. monitoring Aug 20, 2025, 08:17 PM UTC

    We are seeing further degradation in the system and are investigating

  7. monitoring Aug 20, 2025, 08:29 PM UTC

    We have identified a database system outage and are working with our engineers to restore the system.

  8. monitoring Aug 20, 2025, 09:05 PM UTC

    We have brought services back online and are continuing to monitor for stability.

  9. resolved Aug 20, 2025, 10:01 PM UTC

    This incident has been resolved. We will continue to monitor for stability.

Read the full incident report →