@NodeStatus

We have retired from using Twitter/X. For status updates, please see our status page at https://xitter.cf/t.co/Av2GpU03oh

 NYC - LA - ATL - SEA - NL
status.ramnode.com
Joined May 2013
  • Tweets2K
  • Following49
  • Followers2.2K
We will no longer be using Twitter/X to announce status updates. Please see our status page at status.ramnode.com

RamNode status

Welcome to RamNode status page for real-time and historical data on system performance.

status.ramnode.com
1
898
Investigating small network outage in our Seattle location
4
884
The problem has been resolved.
608
Waiting on remote hands to reseat a cable in one of our routers in Seattle
1
818
Update on issues with atlshared6: shared.status.ramnode.com/in…
1
774
LASKVM9 is having issues. Please see: kvm.status.ramnode.com/incid…
1
1
601
Investigating possible hardware issue with node NLSVZ74
561
Issues with LA storage are resolved.
405
We are currently experiencing issues with storage in our LA region. Current ETA: 2 hours
385
Investigating Cloud-related network outage in LA
2
519
We're aware of a switch failure in one of our cabs in LA. DC staff are notified and working on a resolution.
406
Network access has been restored in ATL
2
8
561
The facility is currently investigating possible damaged fiber
1
3
483
We just received this from our DC partner "It appears your router is still powered up. We believe this may be an issue with the physical fiber uplink. We are investigating and will update you shortly."
2
3
2
733
We have opened a priority ticket with our DC partner in Atlanta
2
488
We are aware of networking issues in ATL and are working on a resolution.
1
1
2
458
Investigating network outage in ATL
4
2
5
712
Seems like an issue with our primary ATL router. Still troubleshooting the issue
1
2
379
We will be performing emergency network maintenance in LA on 5/11 at 3AM EST (Router reboot, ~15m downtime) and 9AM EST (~3m downtime).
1
389
We are currently experiencing an issue on ATLSVZ79 vz.status.ramnode.com/incide…
378
Load more