All Systems Operational

DartNode Backbone · US Network

All systems operational.

Live health of every point of presence, backbone fiber route, upstream transit session and core service across AS399646.

6/6
POPs online
99.48%
90-day uptime
25.6 ms
avg backbone

Live Network Map

AS399646 · REAL-TIME
25.6 msavg backbone
6/6pops online

Points of Presence

BOSBoston, MA
44.1 ms
RTT
99.97%
30d
99.97%
90d
DCWashington, DC
54.6 ms
RTT
100.00%
30d
100.00%
90d
HOUHouston, TX
4.0 ms
RTT
100.00%
30d
100.00%
90d
KCKansas City, MO
16.2 ms
RTT
99.95%
30d
99.94%
90d
LAXLos Angeles, CA
50.6 ms
RTT
97.98%
30d
97.98%
90d
MCOOrlando, FL
50.5 ms
RTT
99.51%
30d
99.51%
90d

Backbone Fiber Routes

RouteStatusLatency24h
BOS ⟷ DC BOS-DC online 11.4 ms graph →
KC ⟷ BOS KC-BOS online 28.7 ms graph →
KC ⟷ HOU KC-HOU online 17.2 ms graph →
KC ⟷ LAX kc-lax online 35.3 ms graph →
KC ⟷ MCO KC-MCO online 35.5 ms graph →

Upstream Transit

COGENT AS174
online
HOU LAX MCO
3 peering points
Ezee Fiber AS35847
online
HOU
1 peering point
HE AS6939
online
BOS
1 peering point
Wholesale Internet AS32097
online
KC
1 peering point

Core Services

Core Services

BGP Control System 99.50%
DartNode Shield 100.00%
DartNode.com 97.09%
IP Address Management 99.79%
IPMI Relay 100.00%
Job Runner 100.00%
SMTP Relay 100.00%

Active Incidents

major N15 Drive Failure CASE #145 Oct 16 · 19:11 CT
updateHello everyone, We have a significant progress update regarding the data recovery phase for this case.Our technical team has officially finalized the recovery and extraction process from the affected drive. We are now actively configuring the delivery system and preparing secure archives so affected users can access and retrieve their recovered files. Once this distribution system is ready, we will post another update with complete, step-by-step instructions on how to access and download your data. Thank you again for your patience as we finalize this last stage. Oct 26 · 17:13 CT
updateHello team, The node shutdown and final sync have been completed successfully. All associated services are back online and fully operational. Thank you for your patience and support throughout this maintenance window. Oct 22 · 00:13 CT
updateHello,Server Shutdown will begin in 5 minutes.  Oct 21 · 23:59 CT
updateHello Everyone,We will briefly bring down the node for a final sync today at 19:00 CDT / 00:00 UTC. All affected services have already been redeployed. We’ll notify everyone right before taking it down and as soon as it's back online.Thanks for your understanding! Oct 21 · 23:09 CT
updateHello everyone, We apologize for the delay and any inconvenience this situation has caused. Our engineering team has replaced the faulty drive, and all system operations have returned to nominal performance. While our team worked diligently to minimize customer impact, unfortunately, not all services could be fully recovered directly onto the node. What This Means for Affected Services: If your service was impacted, you will likely see a fresh VM deployed in your dashboard. Data Recovery Phase: Our team is actively working to extract all possible data from the damaged drive. Once this extraction process is complete, we will deliver the recovered files to all affected customers. We will keep this case open and continue posting progress updates until all recovered data has been delivered. Thank you for your continued patience and understanding! If you have any questions, please reply directly to your support ticket or reach out to our team. Oct 20 · 20:45 CT
investigatingOur team has identified that a drive (/dev/sdc) in the system is in a failed state. To prevent further issues and restore the system to full health, we are establishing an emergency maintenance window, effective immediately. Please be advised that customers may experience temporary downtime while we replace the drive and synchronize the array. We will provide another status update as soon as the restoration is complete. Oct 16 · 19:11 CT
major ryzen1 Node VMs Unresponsive / Restoration Failures CASE #144 Oct 14 · 06:51 CT
updateHello everyone, A brief update on our progress: the recovery team is still actively working on extracting files from the failed drive. Due to the delicate nature of recovering data from degraded storage, the process continues to run slowly and carefully to prevent file corruption. We remain focused on retrieving as much usable data as possible and will post another update the moment extraction is complete. We appreciate your continued patience. Oct 26 · 15:56 CT
updateHello everyone, A brief update on our progress: the recovery team is still actively working on extracting files from the failed drive. Due to the delicate nature of recovering data from degraded storage, the process continues to run slowly and carefully to prevent file corruption. We remain focused on retrieving as much usable data as possible and will post another update the moment extraction is complete. We appreciate your continued patience. Oct 26 · 15:56 CT
updateHello everyone, We wanted to provide a quick update on this ongoing case. As you may have already noticed in your dashboard, all service redeployments have now successfully completed. Data Recovery Progress:Our technical team is actively working on recovering data from the failed drive. Because we are taking extreme care during the extraction process to maximize data integrity, this phase may take some time. Once the recovery process is complete, we will organize and provide all retrieved data to each affected user. We truly appreciate your continued patience and will share further updates as soon as we receive progress reports from the recovery team. Oct 20 · 20:39 CT
updateHello, Node Shutdown will begin in 5 minutes. Thank you    Oct 19 · 00:09 CT
updateHello Everyone, We will need to power down the server to remove the faulty drive for further recovery efforts.  Server shutdown will happen about 07:00 PM CDT / 12:00 AM UTC.  We will announce it here before the shutdown. Thank you    Oct 18 · 22:04 CT
updateHello everyone, The node is back online and service redeployments are now actively in progress. Fresh Builds & Backups: Once your server redeploys, you can restore your data right away using any manual snapshots saved in your dashboard. Drive Recovery: We have also officially started the data extraction process on the faulty drive to recover files for affected accounts. We will keep everyone posted on this thread as we get more progress updates from the recovery team. Feel free to contact support if you need help Oct 15 · 04:23 CT
updateHello everyone, We are following up on our previous update regarding the node's drive failure. Upon closer inspection, the hardware degradation on the storage array is more severe than initially anticipated. Service Provisioning & Restores: To restore connectivity as quickly as possible, all affected instances will be redeployed as fresh installations. Manual Snapshots/Backups: Please note that every account includes 3 free manual backup/snapshot slots in your dashboard. If you previously created a snapshot of your server, you will be able to use it to restore your data immediately as soon as the fresh node comes back online. Data Recovery Efforts:Once the node is back online and new instances are provisioned, our engineering team will attempt a physical data extraction from the damaged drive. If we are able to successfully recover any data, we will provide it to affected customers as a downloadable file so you can manually retrieve your files and VMs. We sincerely apologize for the disruption and inconvenience this hardware failure has caused. We will continue to post updates here as the process moves forward. Please feel free to reach out to our support team if you have any questions Oct 14 · 22:15 CT
updateHello,I'm about to power off the Node. Please Standby  Oct 14 · 17:20 CT
updateHello everyone, The issue has been identified as a drive failure within the storage array. A technician is actively working on the machine, and a brief power-down will be required to swap in a new NVMe drive. We will post another notification shortly before the system is powered off for the drive replacement. Oct 14 · 15:47 CT
investigatingWe are aware of a network issue currently affecting Rz-1. Customers with services in this node may experience intermittent latency, packet loss, or connectivity loss. Our team is actively working to resolve the issue. Further updates will be posted here as soon as they are available. Oct 14 · 06:51 CT
major LA APAC Routing Issues CASE #21 Feb 27 · 13:16 CT
updateGood Afternoon, A quick update on this, we're waiting for the LAX location to get connected, once connected, this should be resolved :) I will keep everyone updated on our progress as we learn more. - Zack Mar 9 · 19:13 CT
updateGood Evening Everyone :)We are working on a few elements to improve LAX Routing and resolve this issue. Please find the details below: A) We're joining Any2West, and plan to peer with multiple APAC transit providers, including CN2 and other providers. This is currently in work and should be completed this upcoming week;B) We're pulling in NTT as a carrier at this location;C) We're working to connect LAX to our backbone network, allowing connectivity to more of our edges as we continue to grow our network.If you have any questions or feedback, feel free to reply to this ticket, and we will take a look.Again thanks for your understanding, and we're working hard to get this resolved- Zack Mar 1 · 02:50 CT
updateAn update around the LAX routing issues, we're working to resolve the connectivity to the POP and are working with a new upstream provider to bring another circuit into the facility. In the meantime, we will be deploying a GRE tunnel to KC and help with APAC routing.- Zack Feb 27 · 18:08 CT
investigatingCustomers in LA are not able to communicate with servers due to routing issues over the Cogent network Feb 27 · 13:16 CT

Scheduled Maintenance

No maintenance currently scheduled.

Incident History

Resolved incidents are archived on a separate page. View incident history →