Is 2600Hz down?

Product match: components.

Read the provider’s incident report

1. 2026-08-17T11:09:49.530-07:00 · resolved

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

2. 2026-08-17T08:58:32.347-07:00 · identified

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

3. 2026-08-17T08:58:25.744-07:00 · identified

   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.

Product match: components.

Read the provider’s incident report

1. 2026-07-15T12:05:54.340-07:00 · resolved

   This incident has been resolved.

2. 2026-07-15T11:57:58.327-07:00 · monitoring

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

3. 2026-07-15T11:47:32.051-07:00 · identified

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

4. 2026-07-15T11:41:28.560-07:00 · investigating

   We are continuing to investigate this issue.

5. 2026-07-15T11:40:16.682-07:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2026-07-12T16:19:10.766-07:00 · resolved

   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.

2. 2026-07-12T14:51:50.047-07:00 · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-02-20T11:33:46.650-08:00 · resolved

   This incident has been resolved.

2. 2026-02-20T10:35:15.949-08:00 · investigating

   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.

3. 2026-02-20T10:15:10.638-08:00 · investigating

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

4. 2026-02-20T10:09:21.451-08:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2026-01-28T09:23:58.580-08:00 · resolved

   This incident has been resolved.

2. 2026-01-27T16:13:07.643-08:00 · monitoring

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

3. 2026-01-27T12:26:33.327-08:00 · identified

   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.

Product match: components.

Read the provider’s incident report

1. 2025-11-14T09:46:12.193-08:00 · resolved

   This incident has been resolved.

2. 2025-11-13T12:39:09.266-08:00 · monitoring

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

3. 2025-11-13T12:28:41.057-08:00 · investigating

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

4. 2025-11-13T12:14:24.665-08:00 · investigating

   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.

5. 2025-11-13T12:08:23.323-08:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2025-09-02T12:16:50.986-07:00 · resolved

   This incident has been resolved.

2. 2025-09-02T10:11:20.907-07:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2025-08-20T15:01:58.648-07:00 · resolved

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

2. 2025-08-20T14:05:41.261-07:00 · monitoring

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

3. 2025-08-20T13:29:21.455-07:00 · monitoring

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

4. 2025-08-20T13:17:24.175-07:00 · monitoring

   We are seeing further degradation in the system and are investigating

5. 2025-08-20T12:30:20.930-07:00 · monitoring

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

6. 2025-08-20T12:23:05.995-07:00 · monitoring

   We are seeing further degradation in the system and are investigating

7. 2025-08-20T05:32:35.967-07:00 · monitoring

   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.

8. 2025-08-20T05:32:00.389-07:00 · investigating

   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.

9. 2025-08-20T03:50:27.218-07:00 · investigating

   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.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-20T22:18:23.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T22:10:00.000Z to 2026-10-20T22:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every 2600Hz feature.

The latest status observation was 2026-10-20T22:03:51.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save 2600Hz in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.