InterNetX logo

Is InterNetX Down?

SaaSLive status, outages, and incident history

No. InterNetX is up right now.

Every monitored InterNetX system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment InterNetX breaks

InterNetX is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official InterNetX status page
How we know: the official InterNetX status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

InterNetX Status Summary

As of 10:12 UTC on 9 November 2026, InterNetX is operational. PulsAPI checked InterNetX's official status page and found 27 of 27 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.99% uptime for InterNetX, counting degraded performance as up. The latest incident, "Disruption - Cloud Server", was on Oct 13, 2026 and lasted 1h 21m.

Cite as: PulsAPI, “InterNetX status”, checked 9 November 2026, 10:12 UTC. https://www.pulsapi.com/services/internetx

InterNetX Component Status

The main InterNetX systems on this page. All 27 are operational right now.

27operational
AutoDNS » API
Operational
AutoDNS » Domain Studio
Operational
AutoDNS » User Interface
Operational

24 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking DDoS Attack Status, Domain Services » MailProxy, Domain Services » Name Service, Domain Services » NodeSecure / Anycast, Domain Services » PROCEED, Domain Services » Redirector, Domain Services » WhoisProxy, Google Cloud Platform Google Kubernetes Engine, Infrastructure » Data Center FFM, Infrastructure » Data Center MUC, Infrastructure » Data Center USA, Infrastructure » DDoS Mitigation, and 12 more.

See all of them free

Component statuses may change independently during partial outages.

Recent InterNetX Outages & Incidents

Incident history from the official InterNetX status page, including resolution updates.

Disruption - Cloud ServerResolved Oct 13, 2026 · 1h 21mResolved

This incident has been resolved. --- [2026-10-13T14:12:14.940+02:00] (identified) 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.

Disruption - AutoDNSResolved Sep 28, 2026 · 2h 20mResolved

This incident has been resolved. --- [2026-09-28T21:42:04.019+02:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-28T19:59:00.234+02:00] (investigating) 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.

Wichtige Änderung für .ru, .su, .xn--p1ai DomainsStarted Sep 18, 2026Investigating

Ohne ü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 .ru-Trustees. Weitere Informationen und nächste Schritte → Wichtige Informationen zur verpflichtenden ESIA-Identifikation für .ru, .рф und .su Domains https://hub.internetx.com/wichtige-informationen-zur-verpflichtenden-esia-identifikation-f%C3%BCr-.ru-.%D1%80%D1%84-und-.su-domains?hs_preview=eipWWDVi-439614008536 Important information on the mandatory ESIA identification for .ru, .рф and .su domains https://hub.internetx.com/important-information-on-the-mandatory-esia-identification-for-.ru-.%D1%80%D1%84-and-.su-domains?hs_preview=NQMcWHSf-439532807382

InterNetX Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a InterNetX incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 5 days with incidentsNov 9

Going further back: InterNetX uptime by month and every recorded InterNetX outage.

Live InterNetX Outage Reports

Problems reported by engineers using InterNetX. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No InterNetX problems reported yet.

Something wrong with InterNetX on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About InterNetX

InterNetX publishes a public status page at status.internetx.com covering 33 components, including User Interface, AutoDNS and Cloud Server. PulsAPI tracks InterNetX outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured InterNetX uptime at 99.99%. Response times, incident history, and SLA tracking for InterNetX are available on the PulsAPI dashboard.

InterNetX Status FAQ

Is InterNetX down right now?

The verdict at the top of this page comes from the latest poll of the official InterNetX status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if InterNetX is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until InterNetX recovers.

How do I check InterNetX uptime history?

PulsAPI tracks InterNetX uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever InterNetX changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect InterNetX outages?

PulsAPI reads the official InterNetX status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual InterNetX components?

Yes. PulsAPI monitors 27 individual InterNetX components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when InterNetX goes down?

Yes. Create a free account and subscribe to InterNetX: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with InterNetX to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot InterNetX problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor InterNetX?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so InterNetX plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track InterNetX with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services