Meteor incident

Meteor App Deployments Affected on Push to Deploy

Minor Resolved View vendor source →

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

Started
Jan 16, 2026, 09:52 PM UTC
Resolved
Jan 19, 2026, 08:43 PM UTC
Duration
2d 22h
Detected by Pingoru
Jan 16, 2026, 09:52 PM UTC

Affected components

P2D - Push To Deploy

Update timeline

  1. investigating Jan 16, 2026, 09:52 PM UTC

    We are currently investigating an issue affecting Push to Deploy for Meteor applications. Users are unable to deploy new or existing Meteor apps using Push to Deploy in the Galaxy Dashboard. As a workaround, you can deploy your Meteor app using the CLI. Check out our documentation for deployment instructions: https://help.galaxycloud.app/en/article/deploy-a-new-meteor-app-using-the-cli-1vzo6do/ Our team is actively investigating the root cause and will provide updates as we have more information. We appreciate your patience.

  2. monitoring Jan 17, 2026, 07:23 PM UTC

    We've restored Push to Deploy functionality for new Meteor app deployments. Users can now deploy new and existing Meteor apps using Push to Deploy in the Galaxy Dashboard. However, some customers may experience an issue where Push to Deploy settings are lost after a commit. If this happens, you'll need to reconfigure your Push to Deploy settings manually in the Galaxy Dashboard.

  3. monitoring Jan 19, 2026, 04:09 PM UTC

    A fix has been implemented for the Push to Deploy issue affecting Meteor apps, including the settings persistence after commits. We're actively monitoring the situation to ensure stability. Thanks for your patience while we worked through this.

  4. resolved Jan 19, 2026, 08:43 PM UTC

    This incident has been resolved.