Misc

Official Status Pages for AI Services: OpenAI, Anthropic, DeepSeek, Google, Azure, AWS

Official status pages to check AI service outages: OpenAI, Anthropic, DeepSeek, Google Cloud, Azure and AWS, with URLs and per-platform scope notes

一句话总结

To check the running status of mainstream AI services, use the six official status pages: OpenAI (status.openai.com), Anthropic (status.anthropic.com), DeepSeek (status.deepseek.com), Google Cloud (status.cloud.google.com), Microsoft Azure (azure.status.microsoft) and AWS (status.aws.amazon.com); outage and recovery times are based on the information published on these pages.

Use Cases ​

  • When AI API calls fail or respond abnormally, check the official status page first to confirm whether the service is down or degraded.
  • During large-scale outages (such as the DeepSeek and Anthropic incidents on October 15, 2026), use status pages as the authoritative source for confirming and tracking recovery.
  • In alert handling, cross-check official status pages with your own monitoring data to distinguish platform issues from local problems.

Steps ​

  1. Open the corresponding official status page (URLs in the table below).
  2. Check the top of the page for current status: Operational, Outage/Degraded, or Maintenance.
  3. Review the incident timeline for each service component to confirm when the outage started and ended.
  4. Subscribe to the page's notification channels (email, RSS, webhook) for subsequent updates.
  5. Once the platform confirms an issue, sync the status-page information into your team's alert records.

Notes ​

  • Coverage differs per page: the OpenAI page covers ChatGPT and the API; Anthropic covers the Claude API and Claude apps; DeepSeek covers the DeepSeek platform and API; Google Cloud covers Vertex AI, Gemini API and other cloud services (shown per region); Azure covers services such as Azure OpenAI; AWS covers services such as Amazon Bedrock.
  • Some pages list status per region (Google Cloud, AWS); select the relevant region when checking.
  • The incident-history sections keep past outage records, useful for verifying the exact time range of a specific incident.
  • A page showing "Available" does not guarantee that your local network path to the service is healthy; combine it with local connectivity checks.

References ​