31st January 2020

Los Angeles-1 API Endpoint AS Loop in communications between Miami and Los Angeles

We have taken our Los Angeles API endpoint down as there is currently a network routing loop causing communications on the return path from some of our locations (namely, Miami) to fail, meaning the API will wrongfully report services as offline and be unable to control them.

Traffic will be routed automatically to other API endpoints, but this may result in slower control panel performance than usual.

We've worked with our transit provider to exclude our routes from the offending upstream.