Home
Explore Cables Locations Map ISP status Shutdowns
Live Live Map Health Latency Deployments by year Pulse Big screen 🖥
Learn Research Guide Methodology

Developers

GeoCables API v1

Read-only JSON access to what we measure ourselves: submarine cable incidents with measured timelines, daily latency aggregates from our own distributed probe network, and live monitoring status. No signup, no key. Free for commercial and research use under CC BY 4.0 - just credit GeoCables with a link.

Base URL: https://geocables.com/api/v1 60 requests / min / IP Responses cached ~10 min CORS: open

Quick start

curl https://geocables.com/api/v1/status
curl "https://geocables.com/api/v1/incidents?status=resolved&limit=5"
curl "https://geocables.com/api/v1/latency?from=2026-09-01&target_country=SG"

Endpoints

EndpointWhat it returnsParameters
GET /incidentsDetected cable incidents: type, severity, status, measured RTT versus baseline, verdict, link to the public incident page. Honest labelling - an anomaly that turned out not to be a fault says so.status (active | monitoring | warning | resolved), limit ≤ 100, offset
GET /incidents/{alert_number}One incident with its full measured timeline (per-event RTT, ratios, descriptions).-
GET /latencyDaily aggregates per probe-city to target: sample count, median, p90, minimum RTT, average hop count. Same columns as the open dataset.from, to (max 92 d), probe_city, target_city, target_country, limit ≤ 1000
GET /statusLive summary: active alerts, routes and measurements over the last 24 h.-
GET /openapi.jsonMachine-readable OpenAPI 3.0 specification.-

Response envelope

{
  "data": [ ... ],
  "meta": {
    "attribution": "GeoCables (https://geocables.com), CC BY 4.0",
    "docs": "https://geocables.com/developers",
    "total": 180, "limit": 25, "offset": 0
  }
}

What is deliberately not here

Cable names, routes and ownership shown on our maps come from TeleGeography. That inventory is their dataset, not ours, so this API does not redistribute it. Incident records reference cable names only as context for our own measurements. Probe and intermediate hop IP addresses are also omitted throughout.

Bulk data and feeds

Need everything at once? The open dataset ships daily CSV/JSON snapshots (raw measurements are kept as a rolling window; daily aggregates go back further, and dataset version history on Kaggle / Hugging Face preserves every snapshot). Prefer push over pull? Subscribe to the incidents RSS feed.

Fair use and contact

The rate limit exists so one script cannot crowd out everyone else. If you need more - a research project, a newsroom dashboard, an integration - write to datasets@geocables.com and we will sort it out. When you publish something built on this API, we would love to see it; attribution with a link to geocables.com is the only requirement.

🌐 Log In

Access your routes, favorites, and API key

Create account Forgot password?