TeraSwitch status history
Current state: operational — “All Systems Operational” per https://www.teraswitchstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do TeraSwitch incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-04 13:09 UTC | Traffic detour - LON/DUB/EWR/NY undersea fiber cable offline | resolved | none | 40 h 42 min |
| 2026-09-03 14:52 UTC | AWS Tokyo - Ongoing AWS traffic detours | resolved | none | 5 h 12 min |
| 2026-08-22 02:45 UTC | EWR/CHI - Fiber cut and Network Reroute | resolved | minor | 11 h 41 min |
| 2026-08-12 05:18 UTC | Internet Outage Event at Multiple Sites | postmortem | critical | 13 h 10 min |
| 2026-07-29 19:15 UTC | Global - Internet Instability | resolved | major | 19 d 22 h |
| 2026-07-28 16:17 UTC | TYO2 - Network Connectivity Issues with R102 Compute Rack | resolved | major | 35 min |
| 2026-07-17 23:45 UTC | SGP2 - Internet Connectivity Loss | resolved | critical | 2 h 12 min |
| 2026-07-08 17:48 UTC | EWR2 - Reported Network Connectivity Issues | resolved | none | 31 min |
| 2026-06-10 00:24 UTC | DUB1/DUB2 - Network connectivity issue - backbone loss | resolved | none | 13 d 18 h |
| 2026-06-04 15:27 UTC | Backbone - Seattle to Tokyo Detour | resolved | minor | 5 h 43 min |
| 2026-05-12 21:18 UTC | Teraswitch Portal / API - VAN1 management temporarily unavailable | resolved | minor | 9 d 21 h |
| 2026-05-07 02:03 UTC | TYO2 - Core Router Reload | resolved | major | 15 d 16 h |
| 2026-04-30 23:33 UTC | TYO1 - Network Connectivity Issue - Single Rack | resolved | major | 17 h 57 min |
| 2026-03-26 22:08 UTC | AMS1 - Loss of Connectivity | postmortem | critical | 7 d 0 h |
| 2026-03-19 21:43 UTC | EWR2 - Network Connectivity Issues | resolved | major | 6 d 0 h |
| 2026-03-17 20:05 UTC | PIT1 - Sporadic Internet Connectivity Issues | resolved | minor | 8 d 1 h |
| 2026-02-20 07:47 UTC | VAN1 - Connectivity Issues | resolved | none | 3 h 45 min |
| 2026-02-20 07:01 UTC | APAC - Loss of Tokyo to Seattle Backbone Paths | resolved | minor | 4 d 8 h |
| 2026-02-19 02:08 UTC | Subsea Cable Fault - Singapore to Europe | resolved | none | 18 d 0 h |
| 2026-02-04 10:45 UTC | Multiple US Backbone Connection Losses | resolved | minor | 30 h 00 min |
| 2026-02-03 19:54 UTC | Teraswitch Console (console.tsw.io) - Inaccessible | resolved | critical | 2 h 43 min |
| 2026-01-30 09:53 UTC | West Coast Packet Loss | resolved | none | 37 min |
| 2026-01-28 14:17 UTC | Transport/Ultra Low Latency Services Impacted | resolved | none | 0 min |
| 2025-12-28 02:19 UTC | SGP1/SGP2 - Backbone Isolation Event | resolved | none | 29 d 11 h |
| 2025-12-05 21:53 UTC | Teraswitch Console - Increased Errors | resolved | minor | 1 h 52 min |
| 2025-11-29 05:21 UTC | Seattle -> Tokyo Cable Fault | resolved | none | 7 h 40 min |
| 2025-11-18 12:08 UTC | Teraswitch Console & API - Increased Errors / Unavailable | resolved | critical | 6 h 00 min |
| 2025-11-14 15:17 UTC | Internet Connectivity Instability | resolved | none | 2 d 22 h |
| 2025-10-29 16:13 UTC | Teraswitch Console (console.tsw.io) - Inaccessible | resolved | critical | 4 h 14 min |
| 2025-10-29 00:20 UTC | New York <-> London Detoured | resolved | none | 16 min |
| 2025-10-01 21:52 UTC | Teraswitch Console / console.tsw.io - Inaccessible | resolved | critical | 1 h 38 min |
| 2025-09-30 19:01 UTC | SLC1 - Elevated Temperatures in Datahall | resolved | none | 19 h 11 min |
| 2025-09-26 00:00 UTC | Singapore <-> Tokyo Detoured | resolved | minor | 122 d 13 h |
| 2025-09-24 19:58 UTC | New Jersey <-> Ashburn Detoured | resolved | none | 11 min |
| 2025-09-04 21:43 UTC | Amsterdam <-> Frankfurt Detoured | resolved | none | 3 h 16 min |
| 2025-09-01 23:18 UTC | Frankfurt - Internet Traffic Diversion | resolved | none | 16 h 07 min |
| 2025-09-01 05:15 UTC | Seattle <-> Tokyo Detoured | resolved | none | 46 d 13 h |
| 2025-08-26 14:22 UTC | SGP1 - Internet Traffic Latency | resolved | minor | 4 h 07 min |
| 2025-08-25 22:13 UTC | Multiple Sites - Network Instability Issues | resolved | minor | 7 d 17 h |
| 2025-08-19 23:00 UTC | Dublin <-> Amsterdam Intra-Market Connectivity Detoured | resolved | none | 9 h 20 min |
| 2025-08-19 08:45 UTC | Frankfurt <-> Amsterdam Intra-Market Connectivity Detoured | resolved | none | 9 h 18 min |
| 2025-08-12 20:19 UTC | New York <-> London Detoured | resolved | none | 7 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
}