InterNetX Outage History

InterNetX is up right now

InterNetX had 21 outages in the last 2 years totaling 1676h 23m of downtime — averaging 0.9 incidents per month.

There were 21 InterNetX outages since June 6, 2024 totaling 1676h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.internetx.com

Major May 19, 2026

Currently there is a known disruption.

Detected by Pingoru
May 19, 2026, 12:58 PM UTC
Resolved
May 20, 2026, 06:18 AM UTC
Duration
17h 19m
Affected: Kubernetes Cluster
Timeline · 4 updates
  1. investigating May 19, 2026, 12:58 PM UTC

    Currently, we are experiencing a disruption. We have taken immediate action to resolve the issue. We apologize for any inconvenience and thank you for your understanding.

  2. identified May 19, 2026, 04:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 19, 2026, 04:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 20, 2026, 06:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 5, 2026

Disruption – denic DNSSEC

Detected by Pingoru
May 05, 2026, 07:00 PM UTC
Resolved
May 06, 2026, 12:06 AM UTC
Duration
5h 5m
Affected: Name Service
Timeline · 4 updates
  1. identified May 05, 2026, 09:14 PM UTC

    The nameservers *.ns1[4-5].net are currently affected due to a technical disruption by denic DNSSEC. DNS resolution for especially .de domains is currently facing partial outages.

  2. identified May 05, 2026, 09:39 PM UTC

    For detailed information you can visit the denic status page at: https://status.denic.de/

  3. monitoring May 05, 2026, 11:38 PM UTC

    denic confirmed that the issue has been resolved. We are monitoring the results.

  4. resolved May 06, 2026, 12:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2026

Incident AutoDNS Portal

Detected by Pingoru
Mar 19, 2026, 05:59 PM UTC
Resolved
Mar 19, 2026, 08:04 PM UTC
Duration
2h 4m
Affected: User InterfaceName ServiceAPIRedirectorMailProxyDomain StudioNodeSecure / AnycastWhoisProxyPROCEED
Timeline · 3 updates
  1. investigating Mar 19, 2026, 05:59 PM UTC

    Currently we are facing issues with reachability of AutDNS Portal. We're investigating the issue.

  2. monitoring Mar 19, 2026, 07:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 19, 2026, 08:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 27, 2026

Maintenance - ISAC

Detected by Pingoru
Jan 27, 2026, 09:43 AM UTC
Resolved
Jan 27, 2026, 10:39 AM UTC
Duration
55m
Affected: User InterfaceAPI
Timeline · 2 updates
  1. investigating Jan 27, 2026, 09:43 AM UTC

    We will be carrying out maintenance work in ISAC. Some functions will be partially restricted during this time. The availability of your domains and servers will not be affected. All services will be fully available again after the maintenance has been finished.

  2. resolved Jan 27, 2026, 10:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 31, 2025

Disruption - AutoDNS

Detected by Pingoru
Dec 31, 2025, 05:22 PM UTC
Resolved
Jan 01, 2026, 03:38 AM UTC
Duration
10h 15m
Affected: User InterfaceName ServiceAPIRedirectorMailProxyDomain StudioNodeSecure / AnycastWhoisProxyPROCEED
Timeline · 4 updates
  1. investigating Dec 31, 2025, 05:22 PM UTC

    Currently we're facing a Disruption in AutoDNS Services. We're investigating the issue.

  2. identified Dec 31, 2025, 06:59 PM UTC

    The issue has been identified and a fix is being implemented.

  3. investigating Dec 31, 2025, 09:34 PM UTC

    We are currently investigating this issue.

  4. resolved Jan 01, 2026, 03:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025

Disruption – Nameserver

Detected by Pingoru
Dec 22, 2025, 07:27 AM UTC
Resolved
Dec 22, 2025, 10:24 AM UTC
Duration
2h 56m
Affected: Name Service
Timeline · 4 updates
  1. investigating Dec 22, 2025, 07:27 AM UTC

    The nameservers c.ns14.net and dns03.ns15.net are currently affected due to a technical disruption. We have already taken appropriate measures and are working hard to resolve the situation. Full services will be available again shortly. We apologize for any inconvenience and thank you for your understanding.

  2. identified Dec 22, 2025, 09:32 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Dec 22, 2025, 09:41 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 22, 2025, 10:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 18, 2025

Partial destruption of some services

Detected by Pingoru
Dec 18, 2025, 10:58 AM UTC
Resolved
Dec 18, 2025, 02:00 PM UTC
Duration
3h 1m
Affected: User InterfaceAPIPROCEED
Timeline · 3 updates
  1. investigating Dec 18, 2025, 10:58 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 18, 2025, 01:59 PM UTC

    We are continuing to investigate this issue.

  3. resolved Dec 18, 2025, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 1, 2025

Disruption - AutoDNS 3.0

Detected by Pingoru
Dec 01, 2025, 02:16 PM UTC
Resolved
Dec 02, 2025, 09:56 AM UTC
Duration
19h 39m
Affected: User InterfaceAPIDomain Studio
Timeline · 4 updates
  1. investigating Dec 01, 2025, 02:16 PM UTC

    AutoDNS is currently experiencing a disruption. For this reason, the services are temporarily restricted. We have taken immediate action to resolve the issue. We apologize for any inconvenience and thank you for your understanding.

  2. investigating Dec 01, 2025, 02:17 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 01, 2025, 04:40 PM UTC

    Mitigation steps are complete. We’ll continue to monitor the platform closely to ensure everything remains stable.

  4. resolved Dec 02, 2025, 09:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 24, 2025

Maintenance work ccTLD registry (Columbia)

Detected by Pingoru
Sep 24, 2025, 10:37 AM UTC
Resolved
Oct 13, 2025, 01:12 PM UTC
Duration
19d 2h
Timeline · 2 updates
  1. investigating Sep 24, 2025, 10:37 AM UTC

    Due to a migration of backend services of the registry operator for Columbia to a new plattform, domain orders for the TLD .co placed between Thursday, October 2, 10:00 UTC and Tuesday, October 7, 10:00 UTC may be executed with a delay. Our services will be available again without restrictions after the maintenance has been completed. Orders that are delayed due to this maintenance will be processed as usual. If you have any questions, please contact Domain Services at: [email protected] / ☎ +49 941 59559 - 482

  2. resolved Oct 13, 2025, 01:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 19, 2025

Disruption - Hosted Services

Detected by Pingoru
Sep 19, 2025, 09:18 PM UTC
Resolved
Sep 19, 2025, 10:45 PM UTC
Duration
1h 27m
Affected: RedirectorData Center MUCKubernetes Cluster
Timeline · 3 updates
  1. investigating Sep 19, 2025, 09:18 PM UTC

    Our Server are currently affected due to a technical disruption – the availability of customer systems on this host system is temporarily restricted. We have already taken appropriate measures and are working hard to resolve the situation. Full services will be available again shortly. We apologize for any inconvenience and thank you for your understanding.

  2. monitoring Sep 19, 2025, 10:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 19, 2025, 10:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 19, 2025

Disruption - ISAC

Detected by Pingoru
Sep 19, 2025, 05:37 PM UTC
Resolved
Sep 19, 2025, 06:06 PM UTC
Duration
28m
Affected: User InterfaceAPI
Timeline · 3 updates
  1. investigating Sep 19, 2025, 05:37 PM UTC

    ISAC is currently experiencing a disruption. For this reason, the services are temporarily restricted. We have taken immediate action to resolve the issue. We apologize for any inconvenience and thank you for your understanding.

  2. monitoring Sep 19, 2025, 05:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 19, 2025, 06:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 15, 2025

Verifizierungen per SMS eingeschränkt / Verifications via text message restricted

Detected by Pingoru
Sep 15, 2025, 08:55 AM UTC
Resolved
Sep 15, 2025, 01:35 PM UTC
Duration
4h 39m
Timeline · 2 updates
  1. investigating Sep 15, 2025, 08:55 AM UTC

    Derzeit kommt es zu Beeinträchtigungen des SMS-Versand. Nutzer die von uns z.B. für Accountverifikationen, DomainSafe oder Monitoring-Nachrichten eine Benachrichtigung/TAN erhalten können keine oder nur zeitlich verzögert erhalten. There are currently disruptions to SMS messaging. Users who receive notifications/TANs from us, e.g. for account verification, DomainSafe or monitoring messages, may not receive them at all or may experience delays.

  2. resolved Sep 15, 2025, 01:35 PM UTC

    Die Störung wurde behoben / The issue is solved

Read the full incident report →

Notice September 2, 2025

Disruption - Cloud Server

Detected by Pingoru
Sep 02, 2025, 08:11 AM UTC
Resolved
Sep 02, 2025, 03:44 PM UTC
Duration
7h 32m
Affected: Cloud ServerBare Metal ServerManaged ServicesReseller Cloud
Timeline · 5 updates
  1. investigating Sep 02, 2025, 08:11 AM UTC

    Our Cloud-Server are currently affected due to a technical disruption – the availability of customer systems on this host system is temporarily restricted. We have already taken appropriate measures and are working hard to resolve the situation. Full services will be available again shortly. We apologize for any inconvenience and thank you for your understanding.

  2. investigating Sep 02, 2025, 09:32 AM UTC

    We are continuing to investigate this issue.

  3. identified Sep 02, 2025, 09:33 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Sep 02, 2025, 11:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Sep 02, 2025, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2025

Disruption - Core Network Services

Detected by Pingoru
Apr 22, 2025, 09:05 PM UTC
Resolved
Apr 22, 2025, 10:31 PM UTC
Duration
1h 26m
Affected: Data Center MUC
Timeline · 3 updates
  1. investigating Apr 22, 2025, 09:05 PM UTC

    Our Core Network at our Munich Datacenter is currently affected due to a technical disruption – the availability of customer systems on this Datacenter is temporarily restricted. We have already taken appropriate measures and are working hard to resolve the situation. Full services will be available again shortly.

  2. investigating Apr 22, 2025, 10:30 PM UTC

    This incident has been resolved.

  3. resolved Apr 22, 2025, 10:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2025

Security Notice - phishing campaign targeting InterNetX customers

Detected by Pingoru
Apr 15, 2025, 01:49 PM UTC
Resolved
May 21, 2025, 10:26 AM UTC
Duration
35d 20h
Timeline · 2 updates
  1. investigating Apr 15, 2025, 01:49 PM UTC

    Security Notice Phishing campaign targeting InterNetX customers with fraudulent payment reminders We are currently observing a phishing campaign targeting InterNetX customers. Fraudulent emails are being sent falsely claiming that an outstanding invoice must be paid promptly in order to avoid service interruptions or additional reminder fees. These messages emphasize that the payment is particularly important for the renewal of your domain. The included link leads to a website not operated by InterNetX and is designed to steal payment information. Please note: InterNetX does not send email reminders requesting urgent payments for domain renewals. We will never ask you to make such payments through links sent via email. If you have any questions or concerns, please contact Domain Services at: email: [email protected] / phone: +49 941 59559 - 482

  2. resolved May 21, 2025, 10:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 20, 2024

.eu Transactions ; Delayed workflows

Detected by Pingoru
Nov 20, 2024, 11:45 AM UTC
Resolved
Nov 23, 2024, 12:07 AM UTC
Duration
2d 12h
Affected: User InterfaceAPI
Timeline · 4 updates
  1. investigating Nov 20, 2024, 12:49 PM UTC

    The .eu registry is currently experiencing disruptions. As a consequence of this, your .eu-transaction are taking longer to process.

  2. investigating Nov 20, 2024, 12:52 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 21, 2024, 11:11 AM UTC

    The causes of the disruptions have been resolved. There may still be longer workflow runtimes for transfers transactions.

  4. resolved Nov 23, 2024, 12:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2024

registry orders will be processed later

Detected by Pingoru
Nov 18, 2024, 03:39 PM UTC
Resolved
Nov 27, 2024, 09:34 AM UTC
Duration
8d 17h
Timeline · 2 updates
  1. investigating Nov 18, 2024, 03:39 PM UTC

    Because of current changes at the .qa registry orders will be processed later, most likely not before the end of November. Domains need to migrate to a local registrar because of this.

  2. resolved Nov 27, 2024, 09:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 27, 2024

Centralnic Registry currently has partial outages. Orders will be executed with a delay.

Detected by Pingoru
Aug 27, 2024, 12:00 PM UTC
Resolved
Aug 27, 2024, 04:25 PM UTC
Duration
4h 25m
Affected: User InterfaceAPI
Timeline · 4 updates
  1. investigating Aug 26, 2024, 02:01 PM UTC

    Centralnic Registry currently has partial outages. Orders will be executed with a delay.

  2. identified Aug 27, 2024, 04:25 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 27, 2024, 04:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 27, 2024, 04:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 26, 2024

AutoDNS Pro: Web Access is restricted.

Detected by Pingoru
Jul 26, 2024, 03:04 PM UTC
Resolved
Jul 26, 2024, 03:14 PM UTC
Duration
10m
Affected: User Interface
Timeline · 3 updates
  1. investigating Jul 26, 2024, 03:04 PM UTC

    AutoDNS Pro platform: Web Access is restricted.

  2. identified Jul 26, 2024, 03:13 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jul 26, 2024, 03:14 PM UTC

    AutoDNS Pro is available without any restrictions.

Read the full incident report →

Major June 17, 2024

Disruption on our cloud server infrastructure

Detected by Pingoru
Jun 17, 2024, 07:26 AM UTC
Resolved
Jun 17, 2024, 09:46 AM UTC
Duration
2h 19m
Affected: Cloud Server
Timeline · 4 updates
  1. investigating Jun 17, 2024, 07:26 AM UTC

    Currently we are facing a disruption regarding our cloud server infrastructure. Services may be affected. We're currently work on a solution.

  2. investigating Jun 17, 2024, 07:27 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 17, 2024, 08:12 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 17, 2024, 09:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2024

Outage Zone Delegation Check DENIC (.de) ; NAST

Detected by Pingoru
Jun 11, 2024, 08:56 AM UTC
Resolved
Jun 11, 2024, 12:03 PM UTC
Duration
3h 7m
Affected: User InterfaceAPI
Timeline · 3 updates
  1. investigating Jun 11, 2024, 10:44 AM UTC

    There is currently a service disruption at .de registry (DENIC). The zone check failed. For this reason please note that there are delays in the response for all .de orders. We kindly ask you to wait for the system response and, if necessary, perform a domain update afterwards if your domain is not connected. Please check also https://status.denic.de for current status of DENIC´s services.

  2. identified Jun 11, 2024, 11:25 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jun 11, 2024, 12:03 PM UTC

    According to information from DENIC, the problem has been resolved. Open orders will be processed shortly.

Read the full incident report →