All Systems Operational
Uplink ? Operational
90 days ago
99.99 % uptime
Today
Metrics Ingestion ? Operational
90 days ago
100.0 % uptime
Today
Schema Publishing ? Operational
90 days ago
100.0 % uptime
Today
Schema Checks ? Operational
90 days ago
100.0 % uptime
Today
GraphQL API ? Operational
90 days ago
100.0 % uptime
Today
Notifications ? Operational
90 days ago
99.99 % uptime
Today
Studio Metrics Dashboard ? Operational
90 days ago
100.0 % uptime
Today
(experimental) Performance Alerts ? Operational
90 days ago
100.0 % uptime
Today
Rover CDN ? Operational
ApolloGraphQL.com ? Operational
Odyssey ? Operational
Studio UI ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
May 26, 2022

No incidents reported today.

May 25, 2022

No incidents reported.

May 24, 2022

No incidents reported.

May 23, 2022
Resolved - This issue has been resolved.
May 23, 15:32 PDT
Monitoring - Users using federation 1.0 composition and `@specifiedBy` directives would get an error saying `Unknown directive "@specifiedBy".`.

This was due to a misconfiguration in federation 1.0 validation logic which used graphql-js 15.0.0 to validate the generated supergraph core schema rather than using graphql-js 15.7.2.

This bug was introduced at 18:20 UTC May 23, and a fix was released at 08:53 UTC May 24.

May 23, 15:32 PDT
May 22, 2022

No incidents reported.

May 21, 2022

No incidents reported.

May 20, 2022

No incidents reported.

May 19, 2022
Resolved - This incident has been resolved.
May 19, 14:30 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 19, 13:07 PDT
Update - We are in the process of rolling out a fix to allow numeric overrides.
May 19, 12:40 PDT
Identified - We are in the midst of validating a fix that we believe will resume accepting numeric input for `from` and `to` overrides for direct API callers.
May 19, 10:09 PDT
Investigating - We are currently in the midst of resolving an issue around input coercion for users of schema checks that are calling our API directly or using the (legacy) Apollo Language Server to perform schema checks. If you are affected, you may receive errors indicating that your `historicParameters.from` and `historicParameters.to` could not be parsed.

To resolve, please wrap these values in quotation marks `"`. We are in the midst of fixing the issue to accept numeric input via the API and will update his page as we make progress.

May 19, 09:34 PDT
May 18, 2022
Resolved - Users that tried to override schema check configuration via Rover, the legacy Apollo CLI client, or used the API directly received 400 errors due to a misconfiguration in scalar parsing. The issue has now been fixed. If you are currently overriding schema check `from` and `to` values manually, please ensure that these are passed as string types rather than integers.
May 18, 15:30 PDT
May 17, 2022
Resolved - At 13:06 Pacific Apollo underwent a production outage for our Studio UI features. Both internally and externally, users logged into Studio were being logged back out after 30 seconds. This outage ended at 13:44.

This was due to a production deploy of some new feature flagging logic, which enables some Enterprise logout functionality. Instead of this functionality being localized, and enabled for testing, we ended up turning this on for everyone. At 13:44, the issue was identified and we promptly disabled the errant feature flag.

We understand the kind of disruption this caused for everyone (not least of which because at Apollo we also dog food our own product and were getting booted after 30 seconds). We will be conducting our post mortem for this in the coming days as we continue to strive to provide you with the best possible service.

As always, we appreciate your patience!

May 17, 13:44 PDT
May 16, 2022

No incidents reported.

May 15, 2022
Update - At this time we are seeing our system operating well within tolerances and are comfortable concluding this maintenance window. We will continue to strive for excellence in what we do, and for transparency in our communications with you. If we see that some errant server in our system is having problems and causing woes for you our customers, we'll let you know.

Till then, thanks as always for your patience!

May 15, 20:05 PDT
Completed - The scheduled maintenance has been completed.
May 15, 20:00 PDT
Verifying - Our main certificate rotation has completed. We are now in the process of making sure that all of the dependencies which talk with the root certificate are upgraded. This is a much less risky operation, and is expected to take some time to complete. We will continue monitoring our progress here during this defined maintenance window, and update you at that time as to whether we are seeing any snags.

At this time, things are still looking rosy, and we are hopeful that disruptions will be minor and well within our SLAs as this wraps up.

May 15, 19:20 PDT
Update - At this time we have begun our certificate rotation internally. We will update you shortly as to the progress, and impacts this may have on our service. At this time we are still operating externally perfectly as normal and will strive during this maintenance window to continue operating as normal with complete transparency.

Thanks all!

May 15, 19:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 19:00 PDT
Scheduled - On Sunday, May 15th, beginning at 19:00 PST for a period of up to one hour, we will be undergoing scheduled maintenance of our infrastructure. Within this window we will be upgrading some of our internal certificates. During that time we expect to be fully operational, but do want to make sure we clearly communicate to everyone that a non-trivial internal change will be taking place.

This cannot affect gateway startup with managed federation, which will continue to work for the duration of this maintenance window.

We will do our best to keep all interruption periods as brief as possible, and we thank you in advance for your patience as we perform this maintenance.

May 4, 14:46 PDT
May 14, 2022

No incidents reported.

May 13, 2022

No incidents reported.

May 12, 2022

No incidents reported.