Total Uptime had 7 outages in the last 2 years totaling 5h 29m of downtime — averaging 0.3 incidents per month.
There were 7 Total Uptime outages since June 16, 2025 totaling 5h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
This issue has been resolved.
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.
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.
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.
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.
Engineers have resolved an upstream provider issue and have redirected traffic at this time. We are monitoring to confirm stability.
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.
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.
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.
This incident is confirmed resolved.
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.
This issue has now been resolved.
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.
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.
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.
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.
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.