» Published on
Network issues seem to have resolved and websites are now working as they should be. We will coordinate with our upstream provider on the cause of the issue and report the update once we have it.
» UpdatedWe have taken additional steps to restart the database server for Texas 2, and Cloud instances that were experiencing 502s are now working as they should be.
We're still investigating network issues related to Texas 1
» UpdatedIssues seem to be specifically related to the internal and outbound network. This should not affect most sites, however, sites that reference external services to function with no timeout will be seeing 502 errors. Some other sites may see degraded performance. We hope to have further updates from the upstream engineers soon.
» UpdatedCustomers with sites on paas1.tx and paas2.tx may be experiencing 502 errors for sites at this time. The outage appears to be a result of a maintenance operation that was being performed in the data center by our upstream provider, IBM Cloud. There was not meant to be any disruption during this operation and this event was unexpected. Their engineers are working to resolve the issue and return network connectivity that caused MySQL to become disconnected. We will provide updates until resolved.
» Updated