All Systems Operational

About This Site

This status page describes the current operational status of Meteor and Galaxy systems.

Note that some aspects of Meteor and Galaxy depend on third-party systems which may have their own outages. While we try to update this page when we learn about outages in systems that we depend on, the status pages for the other system may be updated more quickly. These include:

• Auto-renewing SSL certificates are provided by Let's Encrypt: https://letsencrypt.status.io/
• Support requests are provided by ZenDesk: enter "meteor.zendesk.com" at https://status.zendesk.com/

Galaxy infrastructure Operational
Galaxy management interface Operational
Meteor Developer Accounts server Operational
Meteor package server Operational
Galaxy EU Infrastructure Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Mar 1, 2017

No incidents reported today.

Feb 28, 2017
Resolved - We have not observed any further issues relating to this morning's Amazon S3 outage, so we are tentatively marking this as resolved. Please file a support ticket if you observe any further strange behavior, either relating to this outage or today's unrelated infrastructure upgrade!
Feb 28, 17:10 PST
Monitoring - Amazon's outage seems to have mostly subsided. Deployments and container starts are now operational. We are monitoring to ensure that everything continues to work well. Please contact support if you see any further issues.
Feb 28, 14:32 PST
Identified - Amazon believes they will have improved the situation within another hour, according to the AWS status page.
Feb 28, 13:03 PST
Update - Deploys in the EU cluster appear to fail because our image builder depends on base images stored in Docker Hub, which is also affected by the issue (http://status.docker.com/pages/incident/533c6539221ae15e3f000031/58b5b8c850b734490e0001f2). Starting new containers for existing apps does appear to work in EU.
Feb 28, 10:37 PST
Investigating - Due to ongoing issues in Amazon's S3 system, Galaxy operations that need to read to or write from S3 may fail now. This includes deploying new app versions and starting new containers. Existing containers are unlikely to be affected. We are investigating whether this affects our EU cluster or just our US cluster.
Feb 28, 10:15 PST
Resolved - (Marking this incident as resolved as the doc sites seem entirely fixed — leaving the Galaxy incident open for now.)
Feb 28, 14:33 PST
Monitoring - Amazon's outage seems to have mostly subsided. Deployments and container starts are now operational. We are monitoring to ensure that everything continues to work well. Please contact support if you see any further issues.
Feb 28, 14:32 PST
Update - Amazon believes they will have improved the situation within another hour, according to the AWS status page.
Feb 28, 13:03 PST
Update - Note that this likely affects other MDG services such as the Meteor package server.
Feb 28, 10:16 PST
Identified - Amazon has acknowledged the S3 issue on their status page.

Note that our docs sites are open source, so you can clone and run them on your own machine! See https://github.com/meteor/docs and https://github.com/meteor/galaxy-docs
Feb 28, 10:08 PST
Investigating - Some Meteor sites, such as docs.meteor.com and galaxy-guide.meteor.com, appear to be having issues. This appears to be based on an underlying problem with Amazon S3.
Feb 28, 09:46 PST
Completed - The scheduled maintenance has been completed.
Feb 28, 10:15 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 28, 09:30 PST
Scheduled - Today, we’re starting to slowly roll out some infrastructure changes to how Galaxy runs containers and collects logs from them. These changes will enable some exciting new Galaxy features and improve the reliability of log collection, such as ensuring that the final logged lines before a container crash always get sent to Galaxy’s log servers.

Today’s rollout does not restart any containers; we’ll apply the new configuration only to new containers. Based on our testing, we don’t expect that anyone will notice any major differences in their apps. However, if you do see any new problems with your app, especially related to logs, please file a support ticket to let us know. In the unlikely case that the new configuration prevents your app from working properly, you can turn it off for now by setting the GALAXY_LOGGER environment variable to container in your app’s settings.json.

We’re looking forward to sharing the new features enabled by this new configuration soon!

(The end time on this "maintenance window" has no semantic meaning.)
Feb 28, 09:21 PST
Feb 27, 2017

No incidents reported.

Feb 26, 2017

No incidents reported.

Feb 25, 2017

No incidents reported.

Feb 24, 2017

No incidents reported.

Feb 23, 2017

No incidents reported.

Feb 22, 2017

No incidents reported.

Feb 21, 2017

No incidents reported.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017

No incidents reported.

Feb 16, 2017

No incidents reported.

Feb 15, 2017

No incidents reported.