Cronologia delle interruzioni di Meteor

1. 17 agosto 2026 alle ore 16:30 UTCmonitoring

   Attualmente stiamo vivendo problemi a causa di un'interruzione di GitHub in corso. GitHub ha segnalato la disponibilità degradata in più servizi, inclusi i download di archivio e il contenuto di repository grezzo, che sono attualmente di ritorno errori ad un tasso elevato. Durante le build, si possono riscontrare errori durante l'installazione delle dipendenze. Di conseguenza, la vostra costruzione può fallire in modo intermittente. Deployments innescato da Push to Deploy può anche non iniziare, dal momento che i nuovi impegni raggiungono Galaxy attraverso GitHub webhooks, che sono degradati nello stesso incidente. Ripristinare un dispiegamento può avere successo, anche se i fallimenti possono continuare mentre l'outage è in corso. Questo non è causato da alcun cambiamento sull'infrastruttura di Galaxy, e le operazioni colpite riprenderanno automaticamente una volta GitHub recupera. Stiamo monitorando attivamente lo stato di GitHub e fornirà aggiornamenti, se necessario. Potete seguire i loro aggiornamenti qui: https://www.githubstatus.com

2. 17 agosto 2026 alle ore 22:20 UTCresolved

   Questo incidente è stato risolto. GitHub ha ripristinato i servizi interessati alla loro fine, e costruisce e Push to Deploy distribuzioni su Galaxy sono operativi normalmente. Se un dispiegamento non è riuscito durante l'outage, o se un commit non ha attivato un Push to Deploy build, è possibile attivarlo di nuovo e dovrebbe ora completare come previsto. Ci scusiamo per l'interruzione e vi ringraziamo per la vostra pazienza.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 luglio 2026 alle ore 20:24 UTCinvestigating

   Abbiamo rilevato un insolito aumento del volume di richiesta sul nostro livello proxy, con conseguente errori e aumento della latenza per un sottoinsieme di clienti. Il nostro team di ingegneria è impegnato e priorità di stabilizzazione del servizio. Prossimo aggiornamento entro 30 minuti.

2. 16 luglio 2026 alle ore 20:25 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 16 luglio 2026 alle ore 20:27 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 17 luglio 2026 alle ore 11:01 UTCmonitoring

   Stiamo continuando a monitorare eventuali ulteriori problemi.

5. 17 luglio 2026 alle ore 14:17 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 6 luglio 2026 alle ore 12:36 UTCidentified

   We've identified an issue affecting some customers, where certain apps aren't displaying in the Galaxy Dashboard. Our team is already working on a fix and we'll update this page as soon as it's released. Thanks for your patience in the meantime.

2. 6 luglio 2026 alle ore 21:21 UTCresolved

   The issue affecting app visibility in the Galaxy Dashboard has been resolved. We've released a fix, and apps are now displaying correctly for all affected customers. Thanks for your patience while we worked through this. If you're still seeing any issues, please reach out to our support team.

1. 19 giugno 2026 alle ore 13:15 UTCinvestigating

   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.

2. 19 giugno 2026 alle ore 18:38 UTCresolved

   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.

1. 10 giugno 2026 alle ore 23:32 UTCinvestigating

   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.

2. 11 giugno 2026 alle ore 13:31 UTCresolved

   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.

1. 17 aprile 2026 alle ore 15:26 UTCidentified

   Some customers are hitting an "Empty bundle received" error when deploying to Galaxy Metal via CLI. We've identified the root cause and are working on a fix now. We'll post another update as soon as we have one.

2. 17 aprile 2026 alle ore 16:25 UTCmonitoring

   We've deployed a fix and are watching to confirm the issue is fully resolved.

3. 20 aprile 2026 alle ore 00:01 UTCresolved

   The "Empty bundle received" error affecting CLI deployments to Galaxy Metal has been resolved. Deployments should now complete successfully.

1. 25 marzo 2026 alle ore 12:25 UTCinvestigating

   We are currently investigating an issue affecting some accounts. Symptoms include Galaxy app logs not loading and errors during deployments and database dashboard access. Our team is actively working on a fix. We will provide updates as soon as we have more information.

2. 25 marzo 2026 alle ore 13:12 UTCinvestigating

   We have identified and resolved the issue causing Galaxy app logs to not load for some accounts. Logs should now be displaying correctly. We are continuing to investigate the separate issue affecting deployments and the database dashboard for some users. Further updates will follow.

3. 25 marzo 2026 alle ore 14:01 UTCmonitoring

   A fix has been implemented. We're actively monitoring the situation to ensure stability. Thanks for your patience while we worked through this.

4. 25 marzo 2026 alle ore 14:44 UTCresolved

   This incident has been resolved.

1. 16 gennaio 2026 alle ore 21:52 UTCinvestigating

   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. 17 gennaio 2026 alle ore 19:23 UTCmonitoring

   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. 19 gennaio 2026 alle ore 16:09 UTCmonitoring

   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. 19 gennaio 2026 alle ore 20:43 UTCresolved

   This incident has been resolved.

1. 6 gennaio 2026 alle ore 19:07 UTCinvestigating

   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. 7 gennaio 2026 alle ore 12:25 UTCidentified

   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. 7 gennaio 2026 alle ore 14:40 UTCidentified

   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. 7 gennaio 2026 alle ore 17:48 UTCmonitoring

   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. 8 gennaio 2026 alle ore 11:59 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 alle ore 11:49 UTCinvestigating

   Cloudflare is experiencing instability across multiple regions worldwide. This may cause delays or intermittent failures when downloading Meteor packages and binaries.

2. 19 novembre 2025 alle ore 08:39 UTCresolved

   This incident has been resolved.

1. 20 ottobre 2025 alle ore 09:47 UTCinvestigating

   We are currently experiencing issues with the P2D service in the Galaxy US infrastructure. Initial findings indicate a failure in AWS services that is impacting our systems. AWS has acknowledged problems on their platform: https://health.aws.amazon.com/health/status

2. 20 ottobre 2025 alle ore 09:47 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 20 ottobre 2025 alle ore 10:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 22 ottobre 2025 alle ore 12:53 UTCresolved

   This incident has been resolved.

1. 14 ottobre 2025 alle ore 17:36 UTCinvestigating

   We are observing periods of slowness on PushToDeploy due to machine replacements and reallocation in our execution cluster. During these windows, build and deploy queues may grow and complete more slowly than usual. We are monitoring and adjusting capacity to stabilize the service.

2. 14 ottobre 2025 alle ore 17:36 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 ottobre 2025 alle ore 12:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 15 ottobre 2025 alle ore 12:29 UTCresolved

   This incident has been resolved.

1. 9 ottobre 2025 alle ore 12:57 UTCinvestigating

   We are currently investigating an issue where some users are being redirected to an invalid "Not Found" page (https://beta.galaxycloud.app/undefined/us-east-1) when attempting to access the Galaxy Beta Dashboard. Our team is actively working to identify the root cause and restore normal access as quickly as possible. We appreciate your patience and will provide updates as soon as we have more information.

2. 9 ottobre 2025 alle ore 20:01 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 22 ottobre 2025 alle ore 12:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 22 ottobre 2025 alle ore 12:54 UTCresolved

   This incident has been resolved.

1. 9 luglio 2025 alle ore 18:27 UTCinvestigating

   We are currently experiencing a partial service disruption due to an ongoing incident with Docker Hub. As of Docker Hub’s latest update at 10:24 PDT, their systems are in a read-only state, which affects several key operations on their platform. Due to this outage, the creation of new webapps through our platform is temporarily unavailable. All other services remain fully operational. We are actively monitoring Docker Hub’s status and awaiting full resolution on their side. Once they restore write functionality, the affected features will resume automatically.

2. 9 luglio 2025 alle ore 20:04 UTCresolved

   This incident has been resolved.

1. 12 giugno 2025 alle ore 20:06 UTCinvestigating

   We are currently experiencing issues due to a Cloudflare outage. The following URLs used in our infrastructure are impacted: https://warehouse.meteor.com https://static.meteor.com During builds, you may encounter messages like: Problem downloading Meteor binaries or issues when downloading Atmosphere packages. As a result, your build may fail intermittently or take longer than usual to complete. This is due to Cloudflare instability affecting the delivery of these resources. We are actively monitoring the situation and will provide updates as necessary.

2. 12 giugno 2025 alle ore 22:29 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 giugno 2025 alle ore 22:29 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 12 giugno 2025 alle ore 22:30 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 13 giugno 2025 alle ore 10:01 UTCresolved

   This incident has been resolved.

1. 10 giugno 2025 alle ore 07:32 UTCinvestigating

   We are currently investigating this issue.

2. 10 giugno 2025 alle ore 08:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 giugno 2025 alle ore 10:20 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 10 giugno 2025 alle ore 10:30 UTCresolved

   This incident has been resolved.

1. 15 maggio 2025 alle ore 16:29 UTCinvestigating

   We are currently investigating this issue.

2. 15 maggio 2025 alle ore 16:29 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 maggio 2025 alle ore 16:29 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 15 maggio 2025 alle ore 16:31 UTCresolved

   We experienced a period of instability with the Galaxy Cloud dashboard at beta.galaxycloud.app, which may have prevented users from accessing or managing their applications. Our engineering team identified and resolved the issue quickly. Full functionality has been restored, and we are continuing to monitor the system to ensure continued stability.

1. 12 maggio 2025 alle ore 15:55 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 12 maggio 2025 alle ore 16:45 UTCresolved

   This incident has been resolved.

1. 9 maggio 2025 alle ore 23:19 UTCinvestigating

   We are currently experiencing instability with the Galaxy Cloud dashboard at beta.galaxycloud.app, which may prevent users from accessing or managing their applications. While we work to resolve the issue, you can continue managing your apps using the legacy regional UI: 🌎 Americas: https://galaxy.meteor.com/ 🌏 Asia: https://ap-southeast-2.galaxy.meteor.com/ 🌍 Europe: https://eu-west-1.galaxy.meteor.com/ We appreciate your patience and are working to restore full access as soon as possible.

2. 9 maggio 2025 alle ore 23:57 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 9 maggio 2025 alle ore 23:58 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 9 maggio 2025 alle ore 23:58 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 10 maggio 2025 alle ore 00:15 UTCresolved

   This incident has been resolved.

1. 15 aprile 2025 alle ore 11:50 UTCinvestigating

   We are currently investigating this issue. It seems to be happening for some accounts.

2. 15 aprile 2025 alle ore 13:51 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 aprile 2025 alle ore 15:48 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 16 aprile 2025 alle ore 13:38 UTCresolved

   This incident has been resolved.