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 September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment InterNetX breaks

InterNetX is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official InterNetX status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

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.

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

Partial disruption of internetx.com websiteResolved Aug 12, 2026 · 2h 4mResolved

This incident has been resolved. --- [2026-08-12T19:01:07.750+02:00] (investigating) We are currently investigating this issue.

AutoDNS We will be carrying out scheduled maintenance on our infrastructure during this windowScheduled for Aug 4, 2026 · 3h 0mScheduled

The scheduled maintenance has been completed. --- [2026-08-04T07:00:08.720+02:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-04T06:00:20.018+02:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-07-29T16:13:33.877+02:00] (scheduled) Impact: brief interruptions of a few minutes are possible on the web interface, the API and the EPP interface. API requests that fail during this time will succeed on retry. No data and no orders will be lost. Anything submitted during the maintenance will be processed, in some cases with a short delay. We recommend scheduling time-critical bulk operations outside this window.

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 history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

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 100.00%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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 100.00%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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

2463+ 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