InterNetX status history
Current state: operational — “All Systems Operational” per https://status.internetx.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do InterNetX incidents last?
From 19 incidents with a vendor-posted start and resolve time. Longest on record: Disruption - AutoDNS 3.0 — 19.6 h (2025-12-01 14:16 UTC). Excluded, never estimated: 3 scheduled maintenance. 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 (22)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-12 17:01 UTC | Partial disruption of internetx.com website | resolved | major | 2 h 04 min |
| 2026-06-25 12:45 UTC | Currently there is a known disruption. | resolved | none | 4 h 05 min |
| 2026-06-15 21:00 UTC | Disruption - AutoDNS | resolved | major | 6 h 23 min |
| 2026-06-10 05:47 UTC | Maintenance - AutoDNS | resolved | none | 3 h 28 min |
| 2026-06-04 07:26 UTC | Partial AutoDNS availability issues | resolved | major | 5 h 16 min |
| 2026-05-19 12:58 UTC | Currently there is a known disruption. | resolved | major | 17 h 19 min |
| 2026-05-05 19:00 UTC | Disruption – denic DNSSEC | resolved | major | 5 h 05 min |
| 2026-03-19 17:59 UTC | Incident AutoDNS Portal | resolved | major | 2 h 04 min |
| 2026-01-27 09:43 UTC | Maintenance - ISAC | resolved | critical | 55 min |
| 2025-12-31 17:22 UTC | Disruption - AutoDNS | resolved | major | 10 h 15 min |
| 2025-12-22 07:27 UTC | Disruption – Nameserver | resolved | major | 2 h 56 min |
| 2025-12-18 10:58 UTC | Partial destruption of some services | resolved | major | 3 h 01 min |
| 2025-12-01 14:16 UTC | Disruption - AutoDNS 3.0 | resolved | minor | 19 h 39 min |
| 2025-11-17 23:20 UTC | Disruption - AutoDNS 3.0 | resolved | major | 1 h 51 min |
| 2025-09-24 10:37 UTC | Maintenance work ccTLD registry (Columbia) | resolved | none | 19 d 2 h |
| 2025-09-19 22:45 UTC | Disruption - AutoDNS 3.0 | resolved | major | 7 h 17 min |
| 2025-09-19 21:18 UTC | Disruption - Hosted Services | resolved | major | 1 h 27 min |
| 2025-09-19 21:16 UTC | Disruption - AutoDNS 3.0 | resolved | major | 1 h 28 min |
| 2025-09-19 17:37 UTC | Disruption - ISAC | resolved | major | 28 min |
| 2025-09-15 08:55 UTC | Verifizierungen per SMS eingeschränkt / Verifications via text message restricted | resolved | none | 4 h 39 min |
| 2025-09-09 20:14 UTC | Disruption - AutoDNS | resolved | major | 3 h 10 min |
| 2025-09-02 08:11 UTC | Disruption - Cloud Server | resolved | none | 7 h 32 min |
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 InterNetX with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"internetx"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}