TeraSwitch Outage History

TeraSwitch is up right now

TeraSwitch had 33 outages in the last 2 years totaling 720h 59m of downtime — averaging 1.4 incidents per month.

There were 33 TeraSwitch outages since May 17, 2025 totaling 720h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.teraswitchstatus.com

Minor August 25, 2025

Multiple Sites - Network Instability Issues

Detected by Pingoru
Aug 25, 2025, 10:13 PM UTC
Resolved
Sep 02, 2025, 03:26 PM UTC
Duration
7d 17h
Affected: Intra-Market ConnectivityGlobal External InternetFRA2 - Frankfurt, Germany
Timeline · 3 updates
  1. investigating Aug 25, 2025, 10:13 PM UTC

    Teraswitch is investigating network instability issues affecting multiple sites. We will provide an update as more information becomes available.

  2. identified Aug 25, 2025, 10:35 PM UTC

    The issue appears to be localized to a network transport vendor inside Frankfurt. Pass-through traffic would have been affected between cities. We believe that FRA1 and FRA2 were most impacted by this loss. Other providers in the city were affected so we are trying to understand the full scope of the issue. At this time network traffic is returning to normal.

  3. resolved Sep 02, 2025, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 19, 2025

Dublin <-> Amsterdam Intra-Market Connectivity Detoured

Detected by Pingoru
Aug 19, 2025, 11:00 PM UTC
Resolved
Aug 20, 2025, 08:21 AM UTC
Duration
9h 20m
Affected: Intra-Market ConnectivityDUB1 - Dublin, IrelandDUB2 - Dublin, Ireland
Timeline · 2 updates
  1. identified Aug 20, 2025, 12:44 AM UTC

    Due to a fiber cut on the Amsterdam path, Dublin (DUB1/2) traffic is diverted through London.

  2. resolved Aug 20, 2025, 08:21 AM UTC

    The fiber has been restored.

Read the full incident report →

Notice August 19, 2025

Frankfurt <-> Amsterdam Intra-Market Connectivity Detoured

Detected by Pingoru
Aug 19, 2025, 08:45 AM UTC
Resolved
Aug 19, 2025, 06:03 PM UTC
Duration
9h 18m
Affected: Intra-Market ConnectivityAMS1 - Amsterdam, NetherlandsAMS2 - Amsterdam, NetherlandsAMS3 - Amsterdam, NetherlandsFRA2 - Frankfurt, Germany
Timeline · 2 updates
  1. monitoring Aug 19, 2025, 04:41 PM UTC

    Due to a fiber cut, all Amsterdam locations (AMS1/2/3) are diverted through London to get to Frankfurt (FRA1/2). There is no loss to connectivity other than higher latency via the detour.

  2. resolved Aug 19, 2025, 06:03 PM UTC

    The fiber fault has been cleared and traffic is normalized.

Read the full incident report →

Notice August 9, 2025

Dallas <-> Ashburn Disrupted

Detected by Pingoru
Aug 09, 2025, 02:03 AM UTC
Resolved
Aug 11, 2025, 02:28 AM UTC
Duration
2d
Affected: Intra-Market ConnectivityIAD1 - Ashburn, VADAL1 - Dallas, TX
Timeline · 2 updates
  1. investigating Aug 09, 2025, 02:03 AM UTC

    DAL1 IAD1 has lost connectivity. Traffic is diverted to alternative paths. Teraswitch is currently investigating and engaging our wave partners.

  2. resolved Aug 11, 2025, 02:28 AM UTC

    All traffic is normalized.

Read the full incident report →

Notice August 8, 2025

Seattle to Chicago Disrupted, US < > APAC traffic Diverted

Detected by Pingoru
Aug 08, 2025, 02:12 PM UTC
Resolved
Aug 11, 2025, 02:27 AM UTC
Duration
2d 12h
Affected: Intra-Market ConnectivityCHI1 - Chicago, ILSEA1 - Seattle, WATYO1 - Tokyo, JapanTYO2 - Tokyo, Japan
Timeline · 2 updates
  1. identified Aug 08, 2025, 02:12 PM UTC

    SEA1 CHI1 has lost connectivity due to flapping wave service; traffic is diverted to alternative paths. Teraswitch is currently investigating and engaging our wave service providers.

  2. resolved Aug 11, 2025, 02:27 AM UTC

    All traffic is normalized.

Read the full incident report →

Notice July 25, 2025

Network backbone traffic degradation - LON <> EWR

Detected by Pingoru
Jul 25, 2025, 02:54 PM UTC
Resolved
Aug 11, 2025, 02:28 AM UTC
Duration
16d 11h
Affected: Intra-Market ConnectivityEWR2 - Newark, NJLON1 - London, United Kingdom
Timeline · 5 updates
  1. identified Jul 25, 2025, 02:54 PM UTC

    Teraswitch has identified issues relating to a loss of backbone capacity on the LON-EWR path. This loss of capacity was due to an emergency maintenance by the cable provider, causing various traffic shifts both on and off our network. Teraswitch engineering is rerouting traffic to mitigate congestion along alternate routes; customers in EWR2 and other sites may see degraded network performance until this issue is resolved. If you have any questions or concerns, please reach out to Teraswitch Support at [email protected]

  2. monitoring Jul 31, 2025, 09:24 PM UTC

    Our undersea cable provider has restored access early to the cable system. At this time we do not see any issues with network traffic - but it may be possible we will have to divert traffic again.

  3. monitoring Aug 06, 2025, 01:55 PM UTC

    The LON1 EWR2 path remains down while the cable is repaired.

  4. monitoring Aug 06, 2025, 08:00 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 11, 2025, 02:28 AM UTC

    This work is complete on the undersea cables and traffic flows are normalized.

Read the full incident report →

Minor July 1, 2025

AMS1 - Facility Cooling Issue

Detected by Pingoru
Jul 01, 2025, 01:56 PM UTC
Resolved
Jul 01, 2025, 09:04 PM UTC
Duration
7h 7m
Affected: AMS1 - Amsterdam, Netherlands
Timeline · 4 updates
  1. investigating Jul 01, 2025, 01:56 PM UTC

    Teraswitch is monitoring an active cooling issue at our AMS1 site. Ambient temperatures are currently elevated and rising, and the facility has acknowledged an issue. We will continue to monitor the situation and provide updates as they become available.

  2. identified Jul 01, 2025, 03:18 PM UTC

    Our facility provider for AMS1 has confirmed that the data center is having issues keeping up with internal cooling due to abnormally high outside air temperatures in Amsterdam, NL. We recommend that customers prepare for thermal shutdowns if temperatures continue to rise. At this time, we have not detected any loss of availability.

  3. monitoring Jul 01, 2025, 05:12 PM UTC

    Ambient temperatures are now falling within AMS1. We believe that the risk of impact is over, but will continue to monitor the situation and provide updates until temperatures reach nominal levels.

  4. resolved Jul 01, 2025, 09:04 PM UTC

    Ambient temperatures at AMS1 are now nominal once again per Teraswitch monitoring. Our facility provider has confirmed a solution was implemented and the cooling issue is now resolved. We will review the facility RCA once it is published. Teraswitch's network and services remained available throughout the incident. We apologize for any inconvenience caused by this event. If you have any questions, feel free reach out to Teraswitch Support at [email protected].

Read the full incident report →