Major incident
Hypernode: Degraded performance on our nameservers
Oct 28, 2026, 16:05 UTC
started
19:03 UTC
resolved
2 h 58 min
duration
Affected: Hypernode Servers
Current status of Hypernode: Operational — live Hypernode status
Timeline
- Oct 28, 2026, 16:05 UTCinvestigatingWe 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.
- Oct 28, 2026, 16:22 UTCidentifiedIf 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
- Oct 28, 2026, 16:36 UTCmonitoringEarlier, 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.
- Oct 28, 2026, 19:03 UTCresolvedWe have not observed any further DDoS activity targeting the infrastructure nameservers. The situation remains stable, and services are operating normally.
Updates as published by Hypernode (original).
Other services with incidents at the same time
This was part of a wider event: 16 services reported incidents within the hour.
- ITS Network & Systems 17:00 UTC · eforms.ucsd.edu website down
- Nextiva 16:54 UTC · NextivaONE and NextOS Platform Login Issues
- MRI Software 16:54 UTC · Engage Protect - ID Verification - Reported Incident - Resolved
- Untappd 16:52 UTC · Delayed Updates Across Untappd
- IXOPAY 16:46 UTC · Batch in US production Unavailable
- Keller Cloud 16:41 UTC · KW Consumer Service Notification
- Twilio 16:38 UTC · SMS Delivery Delays from a Subset of Twilio Long Codes to Orange Belgium
- Hostinger 16:36 UTC · Emergency Server NL-1211 Maintenance
- Teleport 16:27 UTC · Failing DNS name servers
- Supabase 16:21 UTC · Delayed Log Delivery from 14:10 - 15:30 UTC
- Anthropic (Claude) 16:19 UTC · Elevated errors affecting the Google Calendar connector
- IT 16:08 UTC · Voicemail.nebraska.edu Login is Unavailable
- OverDrive 16:05 UTC · Issue returning Kindle books early
- Resideo 16:05 UTC · T6 - Registration Issues
- sipgate 16:00 UTC · Telefonie für sipgate Kunden, die über MS Teams telefonieren beeinträchtigt
More Hypernode incidents
- October 21, 2026 Critical PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619
- October 13, 2026 Degraded performance upgrading Hypernode's and creating branchers