VulnPulse

クラウド・サービスの障害情報

10月22日(木)今日

  • 解決済み04:49障害・メンテナンスAnthropic (Claude)Anthropic Status

    Degraded performance for Claude Fable 5

    Oct 21 , 20:29 UTC Resolved - The issue affecting other Claude models has been resolved. Oct 21 , 19:49 UTC Investigating - We are investigating elevated errors on requests to Claude Fable 5. We will provide an update as soon as possible.

  • 解決済み01:17障害・メンテナンスGitHubGitHub Status

    Delays for Pull Requests and Webhook deliveries

    Oct 21 , 19:22 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 21 , 19:22 UTC Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed. Oct 21 , 18:52 UTC Update - Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expec…

  • 解決済み01:12障害・メンテナンスSupabaseSupabase Status

    Project lifecycle operations such as project creation, pausing, and restoration, in all regions

    Status: Resolved The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal. Affected components ca-central-1 (Operational) ap-northeast-1 (Operational) ap-southeast-1 (Operational) ap-south-1 (Operational) eu-west-3 (Operational) ap-southeast-2 (Operational) ap-southeast-2 (Operational) us-west-2 (Operational) ap-northeast-1 (Operational) ap-southeast-1 (Operational) ap-northeast-1 (Operational)…

  • 解決済み00:47障害・メンテナンスOpenAIOpenAI Status

    Elevated error rates for gpt-5.6-luna API requests

    Status: Resolved All impacted services have now fully recovered. Affected components Chat Completions (Operational) Responses (Operational)

10月21日(水)昨日

  • 解決済み23:17障害・メンテナンスOpenAIOpenAI Status

    Elevated FedRAMP API error rates for Astra and Sol

    Status: Resolved All impacted services have now fully recovered. Affected components FedRAMP (Operational)

  • 解決済み14:39障害・メンテナンスSupabaseSupabase Status

    Projects stuck in restarting state

    Status: Resolved All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.

  • 解決済み12:28障害・メンテナンスOpenAIOpenAI Status

    Degraded performance in ChatGPT, Codex, and APIs

    Status: Resolved All impacted services have now fully recovered. Affected components Compliance API (Operational) Connectors/Apps (Operational) Batch (Operational) Embeddings (Operational) Deep Research (Operational) Codex Web (Operational) File uploads (Operational) Voice mode (Operational) Chat Completions (Operational) Realtime (Operational) Codex in ChatGPT Desktop (Operational) dots (Operational) GPTs (Operational) Decisions (Operational) Login (Operational) Search (Operational) Conversations (Operational) Images (Operational) Agent (Operational) Login (Operational) Codex API (Operationa…

  • 解決済み08:53障害・メンテナンスFly.ioFly.io Status

    Capacity issues in GRU region

    Status: Resolved We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal. Affected components Remote Builds (Operational) GRU - Sao Paulo, Brazil (Operational)

  • 解決済み02:35障害・メンテナンスOpenAIOpenAI Status

    Authentication errors for some users

    Status: Resolved On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored. Affected components Login (Operational)

10月20日(火)

  • 解決済み23:05障害・メンテナンスGoogle CloudGoogle Cloud Status

    RESOLVED: Multiple services are experiencing issues in the europe-west2 region.

    Incident began at 2026-10-19 23:08 and ended at 2026-10-20 07:00 (all times are US/Pacific ). Summary Multiple services were experiencing issues in the europe-west2 region. Description The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it. If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved. No further updates will be provided here. We will publish an analysis of th…

  • 解決済み03:13障害・メンテナンスSupabaseSupabase Status

    Support Form Errors

    Status: Resolved Ticket creation has remained normal. We re resolving this incident. Affected components Dashboard (Operational)

  • 解決済み01:56障害・メンテナンスGitHubGitHub Status

    Degraded availability for GitHub Actions, GitHub Pages and Webhooks

    Oct 19 , 16:56 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 19 , 16:56 UTC Monitoring - Actions, Pages and Webhooks are operating normally. Oct 19 , 16:30 UTC Update - We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs. Oct 19 , 15:56 UTC Update - We…

10月19日(月)

  • 解決済み23:14障害・メンテナンスOpenAIOpenAI Status

    File Download errors

    Status: Resolved All impacted services have now fully recovered. Affected components Files (Operational) Responses (Operational) Image Generation (Operational) File uploads (Operational) Images (Operational)

10月17日(土)

  • 解決済み16:49障害・メンテナンスSupabaseSupabase Status

    Project creation errors ap-ne1

    Status: Resolved Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region. Affected components ap-northeast-1 (Operational) ap-northeast-1 (Operational)

  • 解決済み14:15障害・メンテナンスFly.ioFly.io Status

    Platform Wide Rolling Host Reboots

    Status: Resolved All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at https://fly.io/status Affected components LAX - Los Angeles, California (US) (Operational) SYD - Sydney, Australia (Operational) Management Plane - SYD (Operational) Management Plane - SIN (Operational) IAD - Ashburn, Virginia (US) (Operational) CDG - Paris, France (Operational) NRT - Tokyo, Japan (Operational) Management Plane - LAX (Operational…

  • 解決済み04:24障害・メンテナンスFly.ioFly.io Status

    Fly-metrics.net Grafana Dashboard Outage

    Status: Resolved The fly-metrics.net: https://fly-metrics.net hosted Grafana and log search instance is now fully reachable. Affected components Metrics (Operational) Logs (Operational)

10月16日(金)

  • 解決済み19:44障害・メンテナンスOpenAIOpenAI Status

    Delayed Costs data in the Compliance API

    Status: Resolved All impacted services have now fully recovered. Affected components Compliance API (Operational)

  • 解決済み03:56障害・メンテナンスGitHubGitHub Status

    CCA Automations are delayed when starting an Automation

    Oct 15 , 18:56 UTC Resolved - We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations. Oct 15 , 18:53 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 15 , 18:34 UTC Update - CCA Automations are experiencing delays when users start an Automation Oct 15 , 18:31 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

  • 解決済み03:56障害・メンテナンスOpenAIOpenAI Status

    Widespread feature degradation

    Status: Resolved All impacted services have now fully recovered. Affected components Login (Operational)

10月15日(木)

  • 解決済み20:33障害・メンテナンスFly.ioFly.io Status

    Elevated errors creating apps and managing secrets

    Status: Resolved Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected. Affected components Machines API (Operational) Deployments (Operational) Customer Applications (Operational)

  • 解決済み11:35障害・メンテナンスFly.ioFly.io Status

    Partial FRA network issues

    Status: Resolved Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes

  • 解決済み05:25障害・メンテナンスSupabaseSupabase Status

    Realtime latency

    Status: Resolved Realtime has fully recovered. Affected components Realtime (Operational)

10月14日(水)

  • 解決済み20:44障害・メンテナンスJavaScript / Node.jsnpm Status

    Issues with login and viewing packages

    Oct 14 , 11:44 UTC Resolved - This incident has been resolved. Oct 14 , 11:33 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 14 , 11:20 UTC Identified - The issue has been identified and a fix is being implemented. Oct 14 , 11:06 UTC Update - We are continuing to investigate the issue. We also observe increased errors in accessing package settings. Oct 14 , 09:29 UTC Investigating - We observed increased errors and latency in login and viewing packages. We are investigating the issue.

  • 解決済み19:58障害・メンテナンスOpenAIOpenAI Status

    Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst

    Status: Resolved All impacted services have now fully recovered. Affected components Images (Operational)

  • 解決済み18:53障害・メンテナンスOpenAIOpenAI Status

    Degraded performance in Codex and ChatGPT Work

    Status: Resolved All impacted services have now fully recovered. Affected components Codex in ChatGPT Desktop (Operational) ChatGPT Work (Operational)

  • 解決済み05:30障害・メンテナンスGitHubGitHub Status

    [Retroactive] Actions workflow run logs delayed

    Oct 13 , 20:30 UTC Resolved - On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.

  • 解決済み03:24障害・メンテナンスSupabaseSupabase Status

    Edge Function Degradation

    Status: Resolved Edge function deployments have remained stable. We are closing the incident. Affected components ap-southeast-1 (Operational) ap-northeast-1 (Operational) us-east-2 (Operational) eu-north-1 (Operational) us-west-2 (Operational) eu-central-2 (Operational) eu-west-2 (Operational) ap-south-1 (Operational) ca-central-1 (Operational) eu-west-3 (Operational) eu-central-1 (Operational) ap-northeast-2 (Operational) ap-southeast-2 (Operational) eu-west-1 (Operational) ap-east-1 (Operational) sa-east-1 (Operational) us-east-1 (Operational) us-west-1 (Operational)

  • 解決済み03:00障害・メンテナンスAnthropic (Claude)Anthropic Status

    Elevated errors on platform.claude.com

    Oct 13 , 18:00 UTC Resolved - This issue has been resolved. Oct 7 , 21:44 UTC Monitoring - We've mitigated the errors loading usage data on platform.claude.com and in the Admin API usage report. While we work on a full fix, the most recent ~30 minutes of usage may take longer to appear on the platform.claude.com. API requests are not affected, and we will provide additional updates here. Oct 7 , 17:28 UTC Identified - We've identified the cause of errors loading usage data. The Admin API usage report has recovered, and fixes for the platform.claude.com Usage and Rate limits pages are in progr…

  • 解決済み02:09障害・メンテナンスDigitalOceanDigitalOcean Status

    App Platform Deployments

    Oct 13 , 17:09 UTC Resolved - Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled back the update and restored the affected nodes. App Platform deploym…

  • 解決済み01:36障害・メンテナンスOpenAIOpenAI Status

    Degraded performance in GPT-6.1 Sol Codex and Work mode

    Status: Resolved We have resolved the issue causing degraded performance with GPT-6.1 Sol in Codex and ChatGPT Work. Affected components Codex Web (Operational) CLI (Operational) VS Code extension (Operational) Codex API (Operational) ChatGPT Work (Operational)

10月13日(火)

  • 解決済み22:50障害・メンテナンスFly.ioFly.io Status

    Historical logs are currently delayed

    Status: Resolved This has been resolved Affected components Logs (Operational)

  • 解決済み10:30障害・メンテナンスSupabaseSupabase Status

    Log ingestion impaired

    Status: Resolved We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation. Affected components Logging & Observability (Operational)

  • 解決済み05:16障害・メンテナンスGitHubGitHub Status

    Incident with Actions, Pull Requests and Issues

    Oct 12 , 20:16 UTC Resolved - On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. The incident was triggered through a latent condition in our noti…

  • 解決済み05:11障害・メンテナンスVercelVercel Status

    Increased build and deployment failures

    Oct 12 , 20:11 UTC Resolved - This incident has been resolved. Oct 12 , 19:56 UTC Monitoring - The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available. Oct 12 , 18:33 UTC Update - Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available. Oct 12 , 16:10 UTC Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpb…

  • 解決済み01:02障害・メンテナンスOpenAIOpenAI Status

    Delayed Costs data in the Compliance API

    Status: Resolved All impacted services have now fully recovered. Affected components Compliance API (Operational)

10月12日(月)

  • 解決済み08:30障害・メンテナンスFly.ioFly.io Status

    Sprite hosting outage

    Status: Resolved From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error. As of 00:45 UTC this incident has been resolved.

  • 解決済み08:29障害・メンテナンスDigitalOceanDigitalOcean Status

    DNS Resolution for Managed Kubernetes

    Oct 11 , 23:29 UTC Resolved - Our Engineering team has resolved the external DNS resolution failures affecting Managed Kubernetes across multiple regions. Applications running on Managed Kubernetes can now resolve external domain names. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience problems, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/ Oct 11 , 22:54 UTC Monitoring - Our Engineering team has implemented a fix to address the intermittent external DNS lookup failures affectin…

10月10日(土)

  • 解決済み11:10障害・メンテナンスSupabaseSupabase Status

    Intermittent connection errors via the connection pooler in us-east-1

    Status: Resolved Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.

  • 解決済み10:37障害・メンテナンスVercelVercel Status

    Delays in Drains, Observability, and Workflow in Washington (iad1)

    Oct 10 , 01:37 UTC Resolved - All services have recovered. Oct 10 , 01:12 UTC Monitoring - Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available. Oct 10 , 00:35 UTC Identified - A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor. Oct 10 , 00:15 UTC Investigating - We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics…

  • 解決済み09:26障害・メンテナンスOpenAIOpenAI Status

    Some ChatGPT content may be unavailable on Android

    Status: Resolved All impacted services have now fully recovered. Affected components Conversations (Operational)

  • 解決済み08:26障害・メンテナンスOpenAIOpenAI Status

    Workspace admins may be unable to manage plugins

    Status: Resolved All impacted services have now fully recovered. Affected components Connectors/Apps (Operational)

10月9日(金)

10月8日(木)

  • 解決済み15:00障害・メンテナンスFly.ioFly.io Status

    LHR network issues

    Status: Resolved This incident has been resolved. Affected components LHR - London, United Kingdom (Operational)

  • 解決済み13:51障害・メンテナンスOpenAIOpenAI Status

    Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs.

    Status: Resolved All impacted services have now fully recovered. Affected components Conversations (Operational) GPTs (Operational) ChatGPT Work (Operational)

  • 解決済み09:03障害・メンテナンスOpenAIOpenAI Status

    Elevated errors with GPT-5.6 Instant in FedRAMP workspaces

    Status: Resolved All impacted services have now fully recovered. Affected components FedRAMP (Operational)

  • 解決済み06:23障害・メンテナンスAnthropic (Claude)Anthropic Status

    Issue with spend limits

    Oct 7 , 21:23 UTC Resolved - We have identified an issue which resulted in some organizations to be incorrectly paused for having reached their spend limit, resulting in refused requests on the Claude API, Claude.ai, Claude Code, Claude Security, and Claude Cowork. This is now resolved.

  • 解決済み03:23障害・メンテナンスOpenAIOpenAI Status

    Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity

    Status: Resolved All impacted services have now fully recovered. Affected components dots (Operational)

  • 解決済み03:06障害・メンテナンスOpenAIOpenAI Status

    Dot in Codex may fail to create new threads

    Status: Resolved All impacted services have now fully recovered. Affected components dots (Operational)

  • 解決済み03:04障害・メンテナンスGitHubGitHub Status

    Incident with Git Operations, Issues, Actions and Pull Requests

    Oct 7 , 18:04 UTC Resolved - On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7 Oct 7 , 18:00 UTC Update - All systems have recovered. We have applied mitigations and do not anticipate another recurrence. Oct 7 , 17:27 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 7 , 17:…

  • 解決済み01:25障害・メンテナンスGitHubGitHub Status

    Incident with Git Operations, Pull Requests and Actions

    Oct 7 , 16:25 UTC Resolved - On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected. In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%,…