SimpleVoIP Outage History

SimpleVoIP is up right now

SimpleVoIP had 6 outages in the last 2 years totaling 53h 4m of downtime, averaging 0.2 incidents per month.

There were 6 SimpleVoIP outages since October 28, 2024 totaling 53h 4m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.simplevoip.us

Major February 20, 2026

Call Completion

Detected by Pingoru
Feb 20, 2026, 07:02 PM UTC
Resolved
Feb 20, 2026, 08:14 PM UTC
Duration
1h 11m
Affected: Core Voice Services
Timeline · 4 updates
  1. investigating Feb 20, 2026, 07:02 PM UTC

    We are investigating reports of some calls not completing on our system. We will provide updates as soon as we have identified the cause and impact of this event.

  2. investigating Feb 20, 2026, 07:13 PM UTC

    We have identified that this issue appears to be related to an upstream carrier and is correlated with the ongoing Cloudflare outage affecting portions of internet routing. As a result, any call routes that traverse infrastructure impacted by the Cloudflare issue may experience disruption — even where the core SimpleVoIP platform remains fully operational. At this time: Outbound calling is fully operational. Inbound calling remains impacted for a subset of DIDs, depending on carrier routing paths. We are actively working with our carrier partners and monitoring the broader Cloudflare incident. We will continue to provide updates as more information becomes available.

  3. monitoring Feb 20, 2026, 07:36 PM UTC

    Inbound calling has been restored and call traffic has normalized as of approximately 10 minutes ago. Upstream carriers, in coordination with Cloudflare, have identified and implemented workarounds for the underlying routing issues that were impacting certain call paths. At this time: Inbound calling is operational Outbound calling remains fully operational We are continuing to monitor traffic closely to ensure stability. We will provide a final resolution update once the upstream incident has been fully closed.

  4. resolved Feb 20, 2026, 08:14 PM UTC

    Call routing has fully stabilized and traffic patterns have returned to normal. The earlier disruption was tied to upstream carrier routing paths correlated with the broader Cloudflare incident. Upstream providers have implemented mitigations and routing has remained stable following those changes. All inbound and outbound calling services are fully operational at this time. We will continue passive monitoring, but no further impact is expected. Thank you for your patience while this was investigated and resolved.

Read the full incident report →

Minor January 27, 2026

Connectivity issue in US-Central region affecting call quality

Detected by Pingoru
Jan 27, 2026, 08:44 PM UTC
Resolved
Jan 28, 2026, 05:47 AM UTC
Duration
9h 3m
Affected: Core Voice Services
Timeline · 3 updates
  1. identified Jan 27, 2026, 08:44 PM UTC

    We are experiencing degraded voice quality and one-way audio issues in the US-Central region due to a CloudFlare issue impacting Chicago. Our engineers have routed traffic to our US-East and US-West datacenters to minimize the impact.

  2. monitoring Jan 27, 2026, 09:03 PM UTC

    Most devices have now moved to unaffected zones, so there should be no additional impact at this time. We'll keep an eye on CloudFlare's Status Page (https://www.cloudflarestatus.com/) to determine when it's safe to return the US-Central traffic to its default route.

  3. resolved Jan 28, 2026, 05:47 AM UTC

    CloudFlare has resolved the upstream issue, so we have moved normal traffic back to US-Central. Please reach out to our Support team if you are experiencing any service issues.

Read the full incident report →

Minor November 13, 2025

Regional Connectivity - US-West

Detected by Pingoru
Nov 13, 2025, 08:21 PM UTC
Resolved
Nov 14, 2025, 04:04 AM UTC
Duration
7h 43m
Affected: Core Voice Services
Timeline · 3 updates
  1. identified Nov 13, 2025, 08:21 PM UTC

    We are experiencing some network connectivity issues in our US-West datacenter. Most phones have already re-registered to a healthy zone, and carrier traffic has been moved to avoid any impact. Calls in progress through US-West may have dropped prior to phone re-registration. There should be no further impact once all phone registrations have finished migrating.

  2. monitoring Nov 13, 2025, 08:49 PM UTC

    We found a fiber-related issue in US-West and have resolved it. Everything should be stable there now. We're going to maintain the zone override until after hours tonight, then we'll revert traffic routing to normal.

  3. resolved Nov 14, 2025, 04:04 AM UTC

    All US-West traffic has been returned to its default route, and everything has been stable since the fiber repair.

Read the full incident report →

Major October 20, 2025

Admin Portal

Detected by Pingoru
Oct 20, 2025, 05:40 PM UTC
Resolved
Oct 21, 2025, 12:22 AM UTC
Duration
6h 41m
Affected: SimpleVoIP Admin Portal
Timeline · 2 updates
  1. identified Oct 20, 2025, 05:40 PM UTC

    Our Admin Portal (https://admin.simplevoip.us) is failing to load a significant portion of the time due to an underlying AWS network issue. Users may see "Too many redirects" or "Gateway timeout" errors when attempting to log in or navigate within the portal. We are working to mitigate this on our end while AWS continues to work on their issue. The core voice platform should be unaffected, and all call traffic and phone registrations appear normal in our monitoring.

  2. resolved Oct 21, 2025, 12:22 AM UTC

    Amazon has declared their incident resolved as of about 90 minutes ago. We saw our web services stabilize for the most part a few hours before.

Read the full incident report →

Major July 31, 2025

Unregistered Phones

Detected by Pingoru
Jul 31, 2025, 11:39 AM UTC
Resolved
Jul 31, 2025, 03:51 PM UTC
Duration
4h 12m
Affected: Core Voice ServicesSimpleVoIP Admin Portal
Timeline · 4 updates
  1. investigating Jul 31, 2025, 11:39 AM UTC

    We are investigating reports of unregistered phones on our system. We will provide updates as soon as we have identified the cause and impact of this event.

  2. identified Jul 31, 2025, 11:45 AM UTC

    There is an issue with the voipwebaccess.com domain that is impacting connectivity for all phones that register through that domain. We are working with our DNS providers to get service restored ASAP.

  3. monitoring Jul 31, 2025, 12:09 PM UTC

    We have resolved the underlying issue with the voipwebaccess.com domain, and phones are starting to re-register. It may take a few more minutes for all phones to come back online.

  4. resolved Jul 31, 2025, 03:51 PM UTC

    At this point 90% of devices affected by this morning's DNS issue with voipwebaccess.com have come back online. If you have a device that has not returned to service yet, please give it a reboot. If that doesn't fix it, please contact our Support team at 855-899-8647 or [email protected] for extended troubleshooting.

Read the full incident report →