Incident history

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

The website and API were unavailable for about 2 minutes (00:55–00:57 UTC) during a planned release of a new version of the site. The MCP server was also briefly unavailable, for about 15 seconds at 00:53 UTC, for the same reason. Requests sent during these windows should be retried. API keys, quotas and data were not affected.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

Game demos were unavailable on 23 September from 05:57 to 06:07 UTC as part of the same outage as the website and API: a routine update picked up an incompatible release of a third-party component, and the service failed to start. A fix was deployed and demos have been working normally since 06:07 UTC. No action is needed; embedded demos will load again on the next page view.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

The data catalog was unavailable on 23 September from 05:57 to 06:07 UTC as part of the same outage as the website and API: a routine update picked up an incompatible release of a third-party component, and the service failed to start. A fix was deployed and the catalog has been operating normally since 06:07 UTC. Please retry any requests that failed during that window. Stored data was not affected.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

The service was unavailable on 23 September from 05:57 to 06:07 UTC (about 9.5 minutes by our own checks). The cause was a routine update: it picked up a new release of a third-party component that was incompatible with our configuration, and the service failed to start after the restart. We pinned the known-good version of the component and deployed a fix; the service has been operating normally since 06:07 UTC. If a request failed or timed out during that window, please retry it. API keys, quotas and stored data were not affected. To prevent a repeat, we are pinning the versions of all third-party components.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This incident has been resolved. The component is operating normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.

This was caused by a planned deployment. While the service was being replaced it stopped accepting requests for a few seconds: our external monitor recorded one failed check at 14:43 UTC, and the next one succeeded. The outage lasted under a minute. Requests sent during that window timed out and can simply be retried. Nothing is required on your side — API keys, quotas and stored data were not affected. The new version is live and all endpoints are responding normally.

We are aware of an incident affecting this component and are investigating. Further updates will follow.