Our engineering team has resolved the issues that were resulting from the faulty network card, and impact is now resolved. All services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Jun 26, 17:04 UTC
Our engineering team has now completed the router code upgrade to help restore stability and resolve the issues due to the faulting network card. We appreciate your patience and will post an update as soon as the issue is fully resolved.
Jun 26, 15:50 UTC
Our engineering team has identified and remediated the immediate issues, which were discovered to be related to a faulting network card. However, we continue to see alerts that indicate there are still intermittent issues with stability. Our engineering team is now executing a router code upgrade that we believe will address the issues and allow us to fully restore service. During this upgrade, users can expect to see brief connectivity issues and interrupted traffic flows. We apologize for the inconvenience and will post another update once the upgrade has completed.
Jun 26, 14:22 UTC
Our engineering team has identified the cause of the issue with networking in our NYC1 region that is currently causing connectivity issues and impacting multiple services, including our Cloud Control Panel and API, and is working on a fix. We will post an update as additional information is available.
Jun 26, 13:31 UTC
Our engineering team continues to investigate the ongoing issues. a networking issue in our NYC1 region. During this time, you may experience intermittent packet loss or increased latency, as well as issues with creating and accessing services and accounts from the Cloud Control Panel or API. We apologize for the inconvenience and will share an update once we have more information.
Jun 26, 12:11 UTC
Our engineering team is investigating a networking issue in our NYC1 region. During this time, you may experience intermittent packet loss or increased latency. We apologize for the inconvenience and will share an update once we have more information.
Jun 26, 11:48 UTC