Total Uptime Outage History

Total Uptime is up right now

Pingoru has recorded 10 incidents for Total Uptime: 7 in the last 12 months and 2 in the last 90 days.

Source: totaluptimestatus.com

10incidents recorded
7last 12 months
2last 90 days
59 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Total Uptime 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 202611 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202612 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 564 (0%)

Incidents, newest first

Minor October 13, 2026 Support panel outage 16m Support Ticket System

Started Oct 13, 2026, 01:10 PM UTC· resolved Oct 13, 2026, 01:27 PM UTC

  1. investigating Oct 13, 2026, 01:10 PM UTC

    Engineers are working to resolve access to our support panel. For any immediate support need, please call us at +1 800.584.1514 option 3 or by using an alternate number from our website.

  2. resolved Oct 13, 2026, 01:27 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor August 26, 2026 Network Degradation - US-E Region 2h 8m Global Network and Backbone, North America - East

Started Aug 26, 2026, 02:29 PM UTC· resolved Aug 26, 2026, 04:37 PM UTC

  1. investigating Aug 26, 2026, 02:29 PM UTC

    We are currently investigating reports of degraded network performance including additional latency and packet loss in the US-E region. Engineers are actively investigating the issue at this time. We will post updates here as they become available. Thank you for your patience as we work to restore service to normal levels as quickly as possible.

  2. investigating Aug 26, 2026, 02:36 PM UTC

    The issue has been identified as a hardware failure in the Ashburn, VA POP. Any customer traffic traversing the device at the time of the failure was automatically rerouted to alternate devices within that POP and/or alternate neighboring POPs. If you are experiencing any issues, please open a support case at https://support.totaluptime.com. We will update this case once restoration is complete.

  3. resolved Aug 26, 2026, 04:37 PM UTC

    This incident has been fully resolved. The impacted hardware has been fully tested, monitored for one hour and brought back into service restoring the Ashburn, VA POP to full operational capacity from N to N+1. If you are experiencing any issues at all, please open a support case at https://support.totaluptime.com.

Read the full incident report →

Minor May 13, 2026 Network Degradation 21m Global Network and Backbone, North America - East, Europe

Started May 13, 2026, 03:08 PM UTC· resolved May 13, 2026, 03:29 PM UTC

  1. investigating May 13, 2026, 03:09 PM UTC

    We are currently investigating reports of degraded network performance including additional latency and packet loss across portions of our network. Engineers are actively investigating the issue at this time. We will post updates here as they become available. Thank you for your patience as we work to restore service to normal levels as quickly as possible.

  2. investigating May 13, 2026, 03:13 PM UTC

    Engineers have resolved an upstream provider issue and have redirected traffic at this time. We are monitoring to confirm stability.

  3. resolved May 13, 2026, 03:29 PM UTC

    We confirm that this issue has been fully resolved at 15:09 UTC and there are no further impacts seen since our corrective actions were taken.

Read the full incident report →

Minor April 2, 2026 Network Degradation - EU-W 52m Global Network and Backbone, Europe

Started Apr 02, 2026, 07:30 PM UTC· resolved Apr 02, 2026, 08:22 PM UTC

  1. investigating Apr 02, 2026, 07:30 PM UTC

    We are currently investigating reports of degraded network performance including additional latency and packet loss across portions of our network in the EU-West region. Engineers are actively investigating the issue at this time. We will post updates here as they become available. Thank you for your patience as we work to restore service to normal levels as quickly as possible.

  2. monitoring Apr 02, 2026, 08:06 PM UTC

    Engineers have isolated the issue to an internal DNS resolution in the Amsterdam environment and have resolved it. We are still monitoring this for further issues.

  3. resolved Apr 02, 2026, 08:22 PM UTC

    This incident is confirmed resolved.

Read the full incident report →

Major February 20, 2026 Network Degradation - US West 1h 10m Global Network and Backbone, North America - West

Started Feb 20, 2026, 06:18 PM UTC· resolved Feb 20, 2026, 07:29 PM UTC

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

    We are currently investigating reports of degraded network performance including additional latency and packet loss across portions of our network in the US-West region. Engineers are actively investigating the issue at this time. We will post updates here as they become available. Thank you for your patience as we work to restore service to normal levels as quickly as possible.

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

    We have observed network instability across a number of upstream providers out of our Los Angeles POP. We have temporarily redirected traffic away from this POP to mitigate the impact to our customers while we investigate further.

  3. resolved Feb 20, 2026, 06:48 PM UTC

    This issue has been resolved. We are monitoring provider stability within the region and after confirming there are no further issues for a period of time, we will bring this POP back into service.

  4. investigating Feb 20, 2026, 07:29 PM UTC

    We received confirmation from Coresite that the ANY2 West internet exchange suffered routing loops causing a reset of the entire exchange. This event affected over 400 networks on the east coast and corresponds with the impact we noticed at the time.

Read the full incident report →

Minor November 11, 2025 Support Panel Access Issues 48m Support Ticket System

Started Nov 11, 2025, 03:29 PM UTC· resolved Nov 11, 2025, 04:17 PM UTC

  1. investigating Nov 11, 2025, 03:29 PM UTC

    We are currently investigating an issue affecting access to the Support Panel from some regions. As soon as we have further information to share, we will update you.

  2. resolved Nov 11, 2025, 04:17 PM UTC

    This issue has now been resolved.

Read the full incident report →

Minor October 16, 2025 Network Degradation United Kingdom 55m Cloud Load Balancing, ADC-as-a-Service, Global Network and Backbone, United Kingdom

Started Oct 16, 2025, 02:21 AM UTC· resolved Oct 16, 2025, 03:16 AM UTC

  1. investigating Oct 16, 2025, 02:21 AM UTC

    We are currently investigating reports of degraded network performance including additional latency and packet loss across portions of our network in the UK. Engineers are actively investigating the issue at this time. We will post updates here as they become available. Thank you for your patience as we work to restore service to normal levels as quickly as possible.

  2. investigating Oct 16, 2025, 02:40 AM UTC

    Engineers have found the issue with a failed line card in a Juniper MX240 peering router in the Slough, UK datacenter. Traffic has been diverted and this card is currently being replaced. Customer impact at this time should now be low, if at all. We will update you as soon as this has been fully restored.

  3. resolved Oct 16, 2025, 03:16 AM UTC

    The line card has been replaced, confirmed fully operational, and traffic is now being brought back to the site. We are resolving this case at this time.

Read the full incident report →

Minor September 10, 2025 Partial platform access issues 7m Totaluptime.com website, Support Ticket System

Started Sep 10, 2025, 02:50 PM UTC· resolved Sep 10, 2025, 02:57 PM UTC

  1. investigating Sep 10, 2025, 02:50 PM UTC

    We are currently investigating an issue affecting access to the Total Uptime website and support panel from some regions. As soon as we have further information to share, we will update you.

  2. resolved Sep 10, 2025, 02:57 PM UTC

    Engineers found an internal load balancing issue and have resolved it. We are currently investigating for a root cause to determine why this happened. However we are resolving this incident since it is no longer customer impacting.

Read the full incident report →