InterNetX Outage History

38 incidents recorded over the last 365 days, 16 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live InterNetX status100.00% uptime history

Every Recorded InterNetX Incident

InterNetX incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026AutoDNS maintenanceDuring this time we will carry out maintenance on the AutoDNS infrastructure to improve the stability of name resolution. No interruption is expected. Existing WebSocket connections (e.g. live notifications in the…1h 0mScheduled
Oct 31, 2026Scheduled maintenance – AutoDNSWe'll have to reschedule this maintenance appointment to a later date8h 0mScheduled
Oct 29, 2026Scheduled maintenance – AutoDNSThe scheduled maintenance has been completed.1h 0mScheduled
Oct 27, 2026Scheduled maintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Oct 22, 2026Maintenance: Security updates across our entire infrastructureThe scheduled maintenance has been completed.24h 0mScheduled
Oct 22, 2026HP security update (CVE-2026-109618 / CVE-2026-109619)The scheduled maintenance has been completed.1h 0mScheduled
Oct 21, 2026PHP security update (CVE-2026-109618 / CVE-2026-109619) on managed serversThe scheduled maintenance has been completed.1h 0mScheduled
Oct 14, 2026Planned infrastructure maintenance – 14.10.2026, 08:00–09:30 CESTOn 21.10.2026, two critical PHP vulnerabilities were published \(CVSS 9.2\). They can allow attackers to run code on the server without logging in. All PHP versions are affected, regardless of the application \(e.g…1h 30mScheduled
Oct 13, 2026Disruption - Cloud ServerThis incident has been resolved.1h 21mResolved
Oct 13, 2026Planned infrastructure maintenance – 13.10.2026, 08:00–09:00 CESTThe scheduled maintenance has been completed.1h 0mScheduled
Sep 28, 2026Disruption - AutoDNSThis incident has been resolved.2h 20mResolved
Sep 18, 2026Wichtige Änderung für .ru, .su, .xn--p1ai DomainsOhne über ESIA verifizierte Inhaber aus Russland oder einem lokalen Treuhänder können .ru, .su, .xn--p1ai Domains nicht mehr verlängert werden. Um Ihre Domains zu sichern, empfehlen wir die Einrichtung eines…—Investigating
Aug 12, 2026Partial disruption of internetx.com websiteThis incident has been resolved.2h 4mResolved
Aug 4, 2026AutoDNS We will be carrying out scheduled maintenance on our infrastructure during this windowThe scheduled maintenance has been completed.3h 0mScheduled
Jul 22, 2026security reboot of your managed serverThe scheduled maintenance has been completed.5h 0mScheduled
Jul 16, 2026AutoDNS Demo (OT&E) Environment: API & Domain StudioThe scheduled maintenance has been completed.2h 0mScheduled
Jul 13, 2026Maintenance - Load balancersThe scheduled maintenance has been completed.2h 0mScheduled
Jul 1, 2026AutoDNS MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jun 25, 2026Currently there is a known disruption.This incident has been resolved.4h 5mResolved
Jun 15, 2026Disruption - AutoDNSThis incident has been resolved.6h 23mResolved
Jun 10, 2026Maintenance - AutoDNSThis incident has been resolved.3h 28mResolved
Jun 8, 2026Maintenance - Migration .giftThe scheduled maintenance has been completed.40h 0mScheduled
Jun 4, 2026Partial AutoDNS availability issuesThis incident has been resolved.5h 16mResolved
May 19, 2026Currently there is a known disruption.This incident has been resolved.17h 19mResolved
May 5, 2026Disruption – denic DNSSECThis incident has been resolved.5h 5mResolved
Mar 19, 2026Incident AutoDNS PortalThis incident has been resolved.2h 4mResolved
Mar 16, 2026Maintenance - migration of backend services of the registry operator for the RADIX TLDs to a new plattformThe scheduled maintenance has been completed.64h 0mScheduled
Jan 28, 2026Maintenance - NetworkinfrastructureThe scheduled maintenance has been completed.2h 0mScheduled
Jan 27, 2026Maintenance - ISACThis incident has been resolved.55 minResolved
Jan 26, 2026Maintenance - Cloud ServerThe scheduled maintenance has been completed.4h 0mScheduled
Dec 31, 2025Disruption - AutoDNSThis incident has been resolved.10h 15mResolved
Dec 22, 2025Disruption – NameserverThis incident has been resolved.2h 56mResolved
Dec 18, 2025Partial destruption of some servicesThis incident has been resolved.3h 1mResolved
Dec 17, 2025Maintenance - NetworkinfrastructureThe scheduled maintenance has been completed.1h 0mScheduled
Dec 4, 2025Maintenance - NetworkinfrastructureThe scheduled maintenance has been completed.2h 0mScheduled
Dec 1, 2025Disruption - AutoDNS 3.0This incident has been resolved.19h 39mResolved
Nov 26, 2025Maintenance - NetworkinfrastructureThe scheduled maintenance has been completed.4h 0mScheduled
Nov 17, 2025Disruption - AutoDNS 3.0This incident has been resolved.1h 51mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next InterNetX incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This InterNetX Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before InterNetX acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single InterNetX outage in this window ran 2d 16h, against a mean recovery of 6h 59m. If you depend on InterNetX in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.