Meteor incident

App Deployments Affected on CLI and Push to Deploy

Meteor experienced a major incident on June 10, 2026 affecting P2D - Push To Deploy and Galaxy US infrastructure and 1 more component, lasting 13h 59m. The incident has been resolved; the full update timeline is below.

Started: Jun 10, 2026, 11:32 PM UTC
Resolved: Jun 11, 2026, 01:31 PM UTC
Duration: 13h 59m
Detected by Pingoru: Jun 10, 2026, 11:32 PM UTC

Affected components

P2D - Push To DeployGalaxy US infrastructureGalaxy EU InfrastructureGalaxy AP Infrastructure

Update timeline

investigating Jun 10, 2026, 11:32 PM UTC

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.
resolved Jun 11, 2026, 01:31 PM UTC

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.