We're currently seeing significantly elevated latency and some packet loss to China from our Seattle network when routing outbound via AS4837. We suspect there is a fiber cut in China Unicom's US network in the San Jose area, this should be resolved soon.
Our CMIN2 network is unaffected apart from a small latency increase.
We're currently seeing instability on Ceranetworks' network which the majority of our network uses, we've already alerted them to the issue and are waiting a fix.
Issues resolved as of 1 hour 47 minutes ago. Software adjustments were made to better cope with DDoS attacks.
We are seeing further general instability affecting all routes globally for Ceranetworks, we're waiting on an update from them.
Our inbound routing via China Telecom is currently down for an unknown reason, we're waiting on Ceranetworks looking into it. China networks except China Mobile will see higher latency/packet loss in the meantime.
No incidents reported
No incidents reported
No incidents reported
No incidents reported
No incidents reported
Our Dallas network is currently offline, as two independently networked cabinets are offline, the problem is likely with our upstream provider but we're investigating.
The network came back up and has been stable since 14:28 UTC after our upstream replaced their switch hardware. We apologise greatly for the inconvenience caused during this extended network disruption event.
The Dallas network has been completely offline for 47 minutes so far, our upstream is already aware of the current incident and simply tells us they're working on it.
No meaningful updates to provide yet, our upstream is still saying they're working on stabilising the malfunctioning switch.
Our upstream has confirmed the outages have been caused by a malfunctioning switch of theirs, they're still working to stabilize it. Continuing to monitor the issue.
We have seen one further outage within the last 5 minutes, there may be further short outages until our upstream resolves the issue. We are currently monitoring the issue.
Network came back up at 01:35 UTC. We'll speak to our upstream about what the cause was.