Vendor Status Watch

← all vendors

TeraSwitch status history

Current state: operational — “All Systems Operational” per https://www.teraswitchstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
8incidents, last 90 days
42incidents on record
Incidents per week, last 12 weeks:

How long do TeraSwitch incidents last?

12.4 hmedian incident duration42 measured
18.0 days90th percentile1 in 10 ran longer
9.6 hmedian, major/critical only12 incidents

From 42 incidents with a vendor-posted start and resolve time. Longest on record: Singapore <-> Tokyo Detoured — 122.6 days (2025-09-26 00:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (42)

StartedIncidentStatusImpactDuration
2026-09-04 13:09 UTCTraffic detour - LON/DUB/EWR/NY undersea fiber cable offlineresolvednone40 h 42 min
2026-09-03 14:52 UTCAWS Tokyo - Ongoing AWS traffic detoursresolvednone5 h 12 min
2026-08-22 02:45 UTCEWR/CHI - Fiber cut and Network Rerouteresolvedminor11 h 41 min
2026-08-12 05:18 UTCInternet Outage Event at Multiple Sitespostmortemcritical13 h 10 min
2026-07-29 19:15 UTCGlobal - Internet Instabilityresolvedmajor19 d 22 h
2026-07-28 16:17 UTCTYO2 - Network Connectivity Issues with R102 Compute Rackresolvedmajor35 min
2026-07-17 23:45 UTCSGP2 - Internet Connectivity Lossresolvedcritical2 h 12 min
2026-07-08 17:48 UTCEWR2 - Reported Network Connectivity Issuesresolvednone31 min
2026-06-10 00:24 UTCDUB1/DUB2 - Network connectivity issue - backbone lossresolvednone13 d 18 h
2026-06-04 15:27 UTCBackbone - Seattle to Tokyo Detourresolvedminor5 h 43 min
2026-05-12 21:18 UTCTeraswitch Portal / API - VAN1 management temporarily unavailableresolvedminor9 d 21 h
2026-05-07 02:03 UTCTYO2 - Core Router Reloadresolvedmajor15 d 16 h
2026-04-30 23:33 UTCTYO1 - Network Connectivity Issue - Single Rackresolvedmajor17 h 57 min
2026-03-26 22:08 UTCAMS1 - Loss of Connectivitypostmortemcritical7 d 0 h
2026-03-19 21:43 UTCEWR2 - Network Connectivity Issuesresolvedmajor6 d 0 h
2026-03-17 20:05 UTCPIT1 - Sporadic Internet Connectivity Issuesresolvedminor8 d 1 h
2026-02-20 07:47 UTCVAN1 - Connectivity Issuesresolvednone3 h 45 min
2026-02-20 07:01 UTCAPAC - Loss of Tokyo to Seattle Backbone Pathsresolvedminor4 d 8 h
2026-02-19 02:08 UTCSubsea Cable Fault - Singapore to Europeresolvednone18 d 0 h
2026-02-04 10:45 UTCMultiple US Backbone Connection Lossesresolvedminor30 h 00 min
2026-02-03 19:54 UTCTeraswitch Console (console.tsw.io) - Inaccessibleresolvedcritical2 h 43 min
2026-01-30 09:53 UTCWest Coast Packet Lossresolvednone37 min
2026-01-28 14:17 UTCTransport/Ultra Low Latency Services Impactedresolvednone0 min
2025-12-28 02:19 UTCSGP1/SGP2 - Backbone Isolation Eventresolvednone29 d 11 h
2025-12-05 21:53 UTCTeraswitch Console - Increased Errorsresolvedminor1 h 52 min
2025-11-29 05:21 UTCSeattle -> Tokyo Cable Faultresolvednone7 h 40 min
2025-11-18 12:08 UTCTeraswitch Console & API - Increased Errors / Unavailableresolvedcritical6 h 00 min
2025-11-14 15:17 UTCInternet Connectivity Instabilityresolvednone2 d 22 h
2025-10-29 16:13 UTCTeraswitch Console (console.tsw.io) - Inaccessibleresolvedcritical4 h 14 min
2025-10-29 00:20 UTCNew York <-> London Detouredresolvednone16 min
2025-10-01 21:52 UTCTeraswitch Console / console.tsw.io - Inaccessibleresolvedcritical1 h 38 min
2025-09-30 19:01 UTCSLC1 - Elevated Temperatures in Datahallresolvednone19 h 11 min
2025-09-26 00:00 UTCSingapore <-> Tokyo Detouredresolvedminor122 d 13 h
2025-09-24 19:58 UTCNew Jersey <-> Ashburn Detouredresolvednone11 min
2025-09-04 21:43 UTCAmsterdam <-> Frankfurt Detouredresolvednone3 h 16 min
2025-09-01 23:18 UTCFrankfurt - Internet Traffic Diversionresolvednone16 h 07 min
2025-09-01 05:15 UTCSeattle <-> Tokyo Detouredresolvednone46 d 13 h
2025-08-26 14:22 UTCSGP1 - Internet Traffic Latencyresolvedminor4 h 07 min
2025-08-25 22:13 UTCMultiple Sites - Network Instability Issuesresolvedminor7 d 17 h
2025-08-19 23:00 UTCDublin <-> Amsterdam Intra-Market Connectivity Detouredresolvednone9 h 20 min
2025-08-19 08:45 UTCFrankfurt <-> Amsterdam Intra-Market Connectivity Detouredresolvednone9 h 18 min
2025-08-12 20:19 UTCNew York <-> London Detouredresolvednone7 d 21 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch TeraSwitch with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "teraswitch"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}