Teraswitch Status

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Identified: Our sub-sea cable vendor has confirmed that repairs should be completed around 9/19/2025.

At this time, Tokyo backbone traffic remains diverted.

Identified: Teraswitch was alerted to a loss to our path between Seattle and Tokyo. We have directed traffic to external paths. We are working with our providers to resolve this.

ULL traffic between Frankfurt and Tokyo may have seen ~5 minutes of degraded connectivity.

Resolved: Our network transport provider was able to roll back their changes with no impact. At a later date they will replace the malfunctioning hardware.

Teraswitch has normalized operations in Frankfurt.

Monitoring: Due to a network transport provider's routine maintenance having an issue, Teraswitch has elected to reduce risk and divert traffic from our backbone crossing through Frankfurt unnecessarily.

At this time Frankfurt traffic will be routing locally and the global backbone will only use Frankfurt if required.

Resolved: This incident has been resolved.

Identified: 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.

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

Resolved: Our network transport provider was able to roll back their changes with no impact. At a later date they will replace the malfunctioning hardware.

Teraswitch has normalized operations in Frankfurt.

Monitoring: Due to a network transport provider's routine maintenance having an issue, Teraswitch has elected to reduce risk and divert traffic from our backbone crossing through Frankfurt unnecessarily.

At this time Frankfurt traffic will be routing locally and the global backbone will only use Frankfurt if required.

Resolved: This incident has been resolved.

Identified: 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.

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

Identified: Our sub-sea cable vendor has confirmed that repairs should be completed around 9/19/2025.

At this time, Tokyo backbone traffic remains diverted.

Identified: Teraswitch was alerted to a loss to our path between Seattle and Tokyo. We have directed traffic to external paths. We are working with our providers to resolve this.

ULL traffic between Frankfurt and Tokyo may have seen ~5 minutes of degraded connectivity.

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Resolved: Our network transport provider was able to roll back their changes with no impact. At a later date they will replace the malfunctioning hardware.

Teraswitch has normalized operations in Frankfurt.

Monitoring: Due to a network transport provider's routine maintenance having an issue, Teraswitch has elected to reduce risk and divert traffic from our backbone crossing through Frankfurt unnecessarily.

At this time Frankfurt traffic will be routing locally and the global backbone will only use Frankfurt if required.

Resolved: This incident has been resolved.

Identified: 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.

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

Resolved: The fiber cut has been restored and routing is now normalized.

Identified: Due to a fiber cut, our backbone has diverted Amsterdam <-> Frankfurt traffic via London.

There is no impact to operations other than higher latency between cities.

Resolved: Our network transport provider was able to roll back their changes with no impact. At a later date they will replace the malfunctioning hardware.

Teraswitch has normalized operations in Frankfurt.

Monitoring: Due to a network transport provider's routine maintenance having an issue, Teraswitch has elected to reduce risk and divert traffic from our backbone crossing through Frankfurt unnecessarily.

At this time Frankfurt traffic will be routing locally and the global backbone will only use Frankfurt if required.

Resolved: This incident has been resolved.

Identified: 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.

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

Identified: Our sub-sea cable vendor has confirmed that repairs should be completed around 9/19/2025.

At this time, Tokyo backbone traffic remains diverted.

Identified: Teraswitch was alerted to a loss to our path between Seattle and Tokyo. We have directed traffic to external paths. We are working with our providers to resolve this.

ULL traffic between Frankfurt and Tokyo may have seen ~5 minutes of degraded connectivity.

Identified: Our sub-sea cable vendor has confirmed that repairs should be completed around 9/19/2025.

At this time, Tokyo backbone traffic remains diverted.

Identified: Teraswitch was alerted to a loss to our path between Seattle and Tokyo. We have directed traffic to external paths. We are working with our providers to resolve this.

ULL traffic between Frankfurt and Tokyo may have seen ~5 minutes of degraded connectivity.