Hypernode logo

Is Hypernode Down?

Cloud InfrastructureLive status, outages, and incident history

No. Hypernode is up right now.

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

OperationalChecked 2m agoLive · every 60s

Know the moment Hypernode breaks

Hypernode 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.

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

Status report

Hypernode Status Summary

As of 15:34 UTC on 14 November 2026, Hypernode is operational. PulsAPI checked Hypernode's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Degraded performance on our nameservers", was on Oct 28, 2026 and lasted 2h 57m.

Cite as: PulsAPI, “Hypernode status”, checked 14 November 2026, 15:34 UTC. https://www.pulsapi.com/services/hypernode

Hypernode Component Status

The main Hypernode systems on this page. All 6 are operational right now.

6operational
General Announcements
Operational
Hipex Platform » Hipex Servers
Operational
Hipex Platform » Hipex Toolset / API / Service Dashboard
Operational

3 more components tracked

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

Also tracking Hypernode Platform » Hypernode Servers, Hypernode Platform » Hypernode Toolset / API / Control Panel, Third-Party Service Providers.

See all of them free

Component statuses may change independently during partial outages.

Recent Hypernode Outages & Incidents

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

Degraded performance on our nameserversResolved Oct 28, 2026 · 2h 57mResolved

We have not observed any further DDoS activity targeting the infrastructure nameservers. The situation remains stable, and services are operating normally. --- [2026-10-28T17:36:00.885+01:00] (monitoring) Earlier, we experienced issues with the nameservers at our infrastructure partner. It has since become clear that these issues were caused by a DDoS attack targeting the nameservers. The attack now appears to have calmed down, and we are seeing operations return to normal levels. We will continue to monitor the situation closely to ensure everything remains stable. For now, things are looking good, and we don't expect any further issues in the short term. We will provide another update if the situation changes. --- [2026-10-28T17:22:01.645+01:00] (identified) If your DNS configuration makes use a CNAME record ending in hypernode.io, the hostname may currently fail to resolve, resulting in downtime for the affected domains. Customers who have configured their DNS using an IPv4 A record are not affected by this issue. If possible, we recommend temporarily replacing your CNAME record with an A record pointing to the appropriate IP address to restore your environment. Please ensure you use the correct IP address for your Hypernode. You can find this by using the following bash command: ``` dig -t A yournode.hypernode.io @nsa.byte.nl +short ``` In the meantime, we remain in close contact with our infrastructure provider and are actively monitoring the situation while they work on a resolution. The Hypernode Team --- [2026-10-28T17:05:13.228+01:00] (investigating) We are aware of the issues currently affecting our platform, which appear to be DNS-related. Our infrastructure partner is treating this as a top priority and is actively working to resolve the issue. We understand that these disruptions are impacting your operations, and we sincerely apologize for the inconvenience. We are doing everything we can to restore the service as quickly as possible.

Critical PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619Resolved Oct 21, 2026 · 198h 7mResolved

This incident has been resolved. --- [2026-10-22T11:56:00.605+02:00] (monitoring) Update: Platform Status Hypernode is fully operational again, and all PHP versions have been patched. We are still working on the remaining updates for Hipex and will provide another update as soon as there is further progress. --- [2026-10-21T20:33:44.148+02:00] (monitoring) PHP Security Patches Completed All PHP versions on the Hypernode platform have now been successfully patched for the vulnerabilities CVE-2026-109618 and CVE-2026-109619. The rollout is complete across all supported and End-of-Life (EOL) PHP versions. Thank you for your patience and understanding throughout the maintenance. We apologize for any inconvenience caused. --- [2026-10-21T18:18:53.294+02:00] (identified) Update on PHP Security Patches Most servers running PHP 8.2 through PHP 8.5 have now been successfully updated and are back online. If your website is still in maintenance mode or is not accessible, please let us know so we can investigate. For the EOL PHP versions, we are still waiting for the required patch packages to become available. As soon as these packages are released, we will proceed with applying the patches and bringing the remaining affected servers back online. Thank you for your patience and understanding. We will share another update as soon as we have further news. --- [2026-10-21T16:52:07.524+02:00] (identified) Update on PHP Security Patches We are now bringing Hypernodes running PHP 8.2 through PHP 8.5 out of maintenance mode. At the same time, we are actively applying the security patches to the EOL PHP versions across the Hypernode platform. These Hypernodes will be brought back online as soon as the patches have been successfully applied. We will continue monitoring the rollout and keep you updated on further progress. Thank you for your patience and understanding. --- [2026-10-21T16:34:12.262+02:00] (identified) Update on PHP Security Patches We are currently rolling out the official PHP security patches across the Hypernode platform. We expect the first websites to be back online by 16:45 CEST. The rollout will continue across the remaining Hypernodes, and we will bring each site back online as soon as the patches have been successfully applied. We appreciate your patience and will keep you updated on further progress. --- [2026-10-21T15:45:56.324+02:00] (identified) Update on PHP Security Patches The official PHP security patches for CVE-2026-109618 and CVE-2026-109619 are now available. We are currently working on implementing the patches on the Hypernode platform and will start rolling them out across our infrastructure shortly. Once the patches have been successfully applied to your Hypernode, we will bring it back online as soon as possible. We will keep you updated on the progress and notify you when the maintenance is completed. Thank you for your patience and understanding. --- [2026-10-21T15:25:36.494+02:00] (identified) Update on PHP Security Patches We are still waiting for the official PHP patches to become available. The expected end of maintenance has been extended to 16:30 CEST. In the meantime, the temporary security measures remain in place on all Hypernodes to mitigate the vulnerabilities. Once the official patches are released, we will apply them as soon as possible and bring any affected Hypernodes back online. No action is required from your side. We will keep you updated as soon as we have more information. --- [2026-10-21T14:20:06.784+02:00] (identified) Due to a current PHP security vulnerability, Hypernode will perform emergency maintenance today. Starting at 14:30 CEST, your Hypernode will be temporarily taken offline, and a maintenance page will be displayed instead of your website. The official PHP security patches are scheduled for release at 15:00 CEST (13:00 UTC). Once the patches have been released and successfully applied, and we have verified that the environment is safe, we will bring your Hypernode back online. We expect the maintenance to last until approximately 15:30 CEST (13:30 UTC). However, if the official patches are delayed or additional time is required to apply them, the maintenance may take longer. No action is required on your part. We will handle the necessary updates and restore your Hypernode as soon as it is safe to do so. Please monitor our status page for updates throughout the maintenance: https://www.hypernode-status.com/ We apologise for the inconvenience and appreciate your understanding as we take the necessary measures to protect your environment. --- [2026-10-21T11:39:51.392+02:00] (identified) Hypernode is addressing two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, announced on October 21, 2026. Under certain conditions, these vulnerabilities could allow attackers to execute malicious code. - Platform-wide mitigation: Hypernode has deployed additional PHP configuration settings across all nodes: - session.upload_progress.enabled = 0 - session.use_strict_mode = 1 - Security patches: Corrected PHP packages will be installed as soon as they become available for the relevant PHP versions. - Extended support: Customers using older PHP versions with Hypernode PHP Extended Support are also covered. - Customer impact: No customer action is required. Customers should not revert the temporary PHP settings themselves. - Potential disruption: PHP restarts may cause brief interruptions, but Hypernode aims to minimise any impact on store availability. The configuration changes are temporary mitigations and do not replace the official security patches.

Degraded performance upgrading Hypernode's and creating branchersResolved Oct 13, 2026 · 2h 38mResolved

This incident has been resolved. --- [2026-10-13T10:32:15.086+02:00] (monitoring) A fix has been implemented and is being monitored --- [2026-10-13T08:46:07.772+02:00] (identified) This issue has been identified, and a fix is being implemented.

Hypernode Uptime History

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

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Hypernode Outage Reports

Problems reported by engineers using Hypernode. 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 Hypernode problems reported yet.

Something wrong with Hypernode on your end?

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

About Hypernode

Hypernode posts its status at www.hypernode-status.com. The page covers 6 components, among them General Announcements, Hipex Servers and Hipex Toolset / API / Service Dashboard. Past incidents and uptime for Hypernode stay on this page, which helps when you want to know how often it has trouble.

Hypernode Status FAQ

Is Hypernode down right now?

The verdict at the top of this page comes from the latest poll of the official Hypernode 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 Hypernode 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 Hypernode recovers.

How do I check Hypernode uptime history?

PulsAPI tracks Hypernode uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Hypernode changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Hypernode outages?

PulsAPI reads the official Hypernode 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 Hypernode components?

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

Can I get alerts when Hypernode goes down?

Yes. Create a free account and subscribe to Hypernode: 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 Hypernode 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 Hypernode problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Hypernode?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Hypernode 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 Hypernode with the rest of your stack

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