Meteor incident

Push to Deploy and GitHub Integration Issue

Major Resolved View vendor source →

Meteor experienced a major incident on January 6, 2026 affecting P2D - Push To Deploy, lasting 1d 16h. The incident has been resolved; the full update timeline is below.

Started
Jan 06, 2026, 07:07 PM UTC
Resolved
Jan 08, 2026, 11:59 AM UTC
Duration
1d 16h
Detected by Pingoru
Jan 06, 2026, 07:07 PM UTC

Affected components

P2D - Push To Deploy

Update timeline

  1. investigating Jan 06, 2026, 07:07 PM UTC

    Some customers are experiencing issues with Push to Deploy. Affected customers are unable to trigger new application deployments automatically via commits, or have lost their GitHub connection entirely within Push to Deploy settings on Galaxy. Our team is investigating the root cause and working on a resolution.

  2. identified Jan 07, 2026, 12:25 PM UTC

    We've identified the root cause and are actively working on a fix. Our team is prioritizing this and will have an update soon. As a workaround, if you're using a Meteor app, you can use the Meteor CLI to deploy in the meantime. Check out our CLI documentation for deployment instructions while we work on restoring Push to Deploy functionality: https://help.galaxycloud.app/en/article/deploy-a-new-meteor-app-using-the-cli-1vzo6do/

  3. identified Jan 07, 2026, 02:40 PM UTC

    We've successfully stabilized Push to Deploy for Web Apps (non-Meteor) applications. We're now prioritizing the resolution for Meteor apps and will have an update soon. If you're using a Meteor app, you can continue using the Meteor CLI to deploy. Check out our CLI documentation for deployment instructions. https://help.galaxycloud.app/en/article/deploy-a-new-meteor-app-using-the-cli-1vzo6do/

  4. monitoring Jan 07, 2026, 05:48 PM UTC

    We've successfully deployed a fix for the Push to Deploy integration issue. Customers can now deploy applications using Push to Deploy for both WebApps and Meteor apps. We're actively monitoring the situation to ensure stability. Thanks for your patience while we worked through this.

  5. resolved Jan 08, 2026, 11:59 AM UTC

    This incident has been resolved.