Galaxy 2.0 Status

This incident has been resolved. Monti APM has identified and addressed the issue on their end, and the service has been restored. Please note that any data inserts that failed during the outage were not recovered, but no additional data loss occurred beyond that window. We apologize for the disruption and thank you for your patience.

We are currently aware of a connectivity issue affecting Monti APM. Customers may notice that Monti APM has stopped collecting data from their applications and may encounter errors in their logs. This issue is originating on Monti APM's end, and their team is actively investigating. We will continue to monitor the situation and provide updates here as we learn more. We apologize for the disruption and appreciate your patience.

This incident has been resolved. The deployment failures affecting CLI and Push to Deploy were most likely caused by an undocumented temporary unavailability in one of our external dependencies. The issue was not caused by any change on Galaxy's infrastructure and resolved on its own as the external service recovered. Deployments via both CLI and Push to Deploy are now operating normally. We apologize for the disruption and thank you for your patience.

We are currently investigating an issue affecting deployments on Galaxy. Customers attempting to deploy via CLI or Push to Deploy (P2D) are encountering the following error: "Deploy failed: Request failed with status code 500." Both deployment methods are currently impacted. Our team is actively working to identify the root cause, and we will provide updates here as soon as we have more information. We apologize for the disruption and appreciate your patience.