Know if a subsea cable is causing
your client's slowdown.
When clients report international slowness, you shouldn't have to guess. CableStatus monitors global subsea cable infrastructure every 15 minutes — so you know within minutes whether it's a global cable event or your own stack. Stop troubleshooting something you can't fix.
Statuspage monitors your services. CableStatus monitors the internet.
Built by a former Colt Technology sales engineer · 11 years in optical & wholesale telecoms
No significant subsea cable events detected in the past 24 hours. Pipeline running every 15 minutes.
| Route | Benchmark | Alert At | Risk |
|---|---|---|---|
| London ↔ New York | ~60ms | >80ms | MEDIUM |
| London ↔ Singapore | ~160ms | >200ms | HIGH ⚠ |
| London ↔ Tokyo | ~230ms | >280ms | MEDIUM |
| New York ↔ São Paulo | ~120ms | >150ms | LOW |
⚠ London↔Singapore: Red Sea corridor (Houthi activity) + Strait of Hormuz (Iran conflict escalation) — dual elevated risk. London↔Tokyo: routes via AAE-1 and SEA-ME-WE also transit Hormuz corridor.
Houthi attacks on Red Sea shipping have repeatedly triggered cable repair vessel rerouting, extending repair windows on the London–Singapore corridor from the typical 14 days to 6–8 weeks. The SEA-ME-WE 5, EIG, and FALCON systems — which carry the bulk of Europe–Asia traffic — all traverse this corridor. HMN Tech and Alcatel Submarine Networks have been forced to route vessels around the Cape of Good Hope, adding 3–4 weeks to standard repair schedules. MSPs and infrastructure teams with clients on UK–Asia routes should treat this corridor as structurally elevated-risk until the security situation stabilises.
The escalating Israel-Iran conflict introduces a materially different risk vector to the Strait of Hormuz chokepoint. Several major subsea cables traverse waters directly adjacent to Iranian territorial control: AAE-1 (Asia Africa Europe 1), IMEWE (India Middle East Western Europe), SEA-ME-WE 5/6, and FALCON all route through the Gulf of Oman approach. Unlike Houthi disruption — which is kinetic damage to shipping — Iranian action could constitute deliberate infrastructure targeting. Iran has previously signalled willingness to disrupt undersea cable infrastructure during geopolitical escalations. A Hormuz cable incident would simultaneously affect London–Mumbai, London–Singapore, and London–Hong Kong corridors, with no Cape of Good Hope rerouting option available for Gulf-transiting systems. MSPs managing clients with international SaaS dependencies on these corridors should treat this as an active, unpriced infrastructure risk — not just a geopolitical headline.
Four-source telemetry pipeline
Every 15 minutes: Cloudflare Radar BGP telemetry monitors 25+ corridor ASNs including Google, Meta, Microsoft and Colt. RIPE Atlas measures live latency between anchor probes. CAIDA IODA detects country-level traffic drops. SubTel Forum captures confirmed repair reports.
Consensus scoring engine
Signals are weighted across sources: BGP trigger (35%) + latency spike (35%) + traffic drop (30%). A BGP anomaly corroborated by a RIPE Atlas latency increase on the same corridor scores above the alert threshold. Single-source noise is suppressed.
Your team knows before clients call
Critical and high-confidence events trigger instant Slack alerts or webhook payloads to your chosen endpoint. Daily email digest at 07:00 UTC for lower-urgency awareness. BGP and latency signals typically surface 10–20 minutes before public reports.
Need programmatic access?
Need cable events delivered directly to your own systems — RMM, PSA, SIEM, or custom dashboards? Register your interest below and we'll reach out as webhook and API integrations ship.
Billed monthly · cancel anytime
- ✓ All regions monitored
- ✓ Slack alerts on critical events
- ✓ Daily email digest
- ✓ 15-minute detection cycle
For MSPs & multi-client teams
- ✓ Everything in Pro
- ✓ Webhook delivery to any endpoint
- ◎ Embeddable widget — coming soon
- ✓ Priority support
Why do I need this if I already have network monitoring?
Your monitoring tools tell you when your own infrastructure is down — servers, routers, uplinks. They cannot tell you if a subsea cable cut in the Red Sea is slowing your clients' international traffic. That gap is where CableStatus sits. When your client in Singapore reports slowness and your stack looks healthy, CableStatus tells you within minutes whether a cable event on the Europe–Asia corridor is the cause. You stop troubleshooting something you cannot fix, and you communicate proactively instead of guessing.
What is the difference between CableStatus and Atlassian Statuspage or Instatus?
Statuspage and Instatus monitor your own services and let you communicate outages to your customers. CableStatus monitors the internet's physical backbone — the 550+ subsea cables that carry 95% of international internet traffic (TeleGeography, 2024). They are complementary, not competing: when a cable event affects your service, CableStatus identifies it as an external cause so you can update your Statuspage with confidence, send a proactive notice to clients, and close the support ticket with evidence.
How quickly will I know about a cable event?
CableStatus runs a four-source consensus pipeline every 15 minutes: Cloudflare Radar BGP telemetry (25+ corridor ASNs), RIPE Atlas latency probes between city pairs, CAIDA IODA traffic analysis, and SubTel Forum industry press. A cable event typically appears in BGP and latency signals 10–20 minutes before it is reported publicly. For MSPs and infrastructure teams, knowing within 15–30 minutes — before your clients call — is the window that matters.
Which regions and corridors do you monitor?
Four primary corridors cover the most business-critical international routes: UK/Europe ↔ US East Coast (Atlantic — MAREA, Hibernia Express, AEConnect-1), UK/Europe ↔ Asia-Pacific via Red Sea (elevated risk since Q4 2023 due to Houthi activity — SEA-ME-WE 5, EIG, FLAG/FALCON), UK/Europe ↔ Japan (SEA-ME-WE 5, FASTER, PC-1), and US ↔ South America (MONET, SAm-1). These corridors affect the majority of international SaaS traffic, cloud connectivity, and business data flows.
How do I receive alerts?
Free accounts receive a daily email digest covering cable status for one monitored corridor. Pro subscribers receive real-time Slack alerts the moment a cable event is classified as degraded or critical — before the daily digest. Agency subscribers can route events directly to custom webhook endpoints, enabling integration with your own dashboards, ticketing systems, or client-facing status pages.
How long does a subsea cable repair typically take?
The average subsea cable repair takes 2–4 weeks from fault detection to full restoration, depending on water depth and weather (International Cable Protection Committee, 2023). Shallow-water faults under 1,000m typically take 10–14 days. Deep-water faults (1,000m–6,000m) average 3–5 weeks. During the repair window, traffic reroutes to backup paths that are slower, more congested, and may cross different regulatory jurisdictions — causing persistent degradation rather than a clean outage.