ChangeIntelIT change radar
Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 254/255 feeds/APIs · 0/409 docs · checked 13:56 UTC Customize Public modeDiscuss ChangeIntel on Discord

Service status

What Microsoft, GitHub, Cloudflare, Ubiquiti, Cisco Meraki, Palo Alto Networks, GitLab, OpenAI, Anthropic, and Google post on their public status pages, read every 5 minutes while something is open. Each incident shows what else was happening and what changed in the same products just before.

RSS

Make this page yours

Choose the providers you depend on and the regions you run in, and what affects you comes first
Providers you depend onall providers
Providers you depend on

None chosen means all.

Regions you run inevery region
Regions you run in

Incidents elsewhere fold away; incidents that name no region always show.

Azure · Americas16
Azure · Europe20
Azure · Asia Pacific18
Azure · Middle East and Africa6
Azure Government6
Azure China6
Azure · Jio2
Azure DevOps8
Cloudflare datacenters6
Google Cloud2
On the overviewincidents that touch my providers and regions
On the overview
Changes apply as you make them.

Ended in the last 7 days

61 incidents · newest first

Today10

Yesterday22

Mon 12 Oct7

Sat 10 Oct2

Fri 9 Oct5

Thu 8 Oct9

Wed 7 Oct6

  • Anthropic (Claude) Issue with spend limits last seen 21:23 UTC unknown

    Posted 7 Oct 21:23 UTCUpdated 6d ago

    Anthropic Claude

    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.

    Around it2 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before

    Elsewhere at the same time

  • OpenAI Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity last seen 18:23 UTC unknown

    Posted 7 Oct 18:23 UTC

    dots

    All impacted services have now fully recovered.

    1 change ChangeIntel noticed
    1. 7 Oct 18:24 UTC ChangeIntel noticed the text change
    Around it4 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time

  • OpenAI Dot in Codex may fail to create new threads last seen 18:06 UTC unknown

    Posted 7 Oct 18:06 UTC

    dots

    All impacted services have now fully recovered.

    2 changes ChangeIntel noticed
    1. 7 Oct 18:09 UTC ChangeIntel noticed the text change
    2. 7 Oct 17:34 UTC ChangeIntel noticed the text change
    Around it3 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time

  • GitHub Incident with Git Operations, Issues, Actions and Pull Requests last seen 18:04 UTC unknown

    Posted 7 Oct 17:17 UTCUpdated 6d ago

    Git OperationsPull RequestsActionsIssues

    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

    6 earlier updates
    1. 7 Oct 18:04 UTCResolvedThis 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.
    2. 7 Oct 18:00 UTCUpdateAll systems have recovered. We have applied mitigations and do not anticipate another recurrence.
    3. 7 Oct 17:27 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
    4. 7 Oct 17:25 UTCUpdateWe observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
    5. 7 Oct 17:25 UTCUpdateWe observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update shortly.
    6. 7 Oct 17:17 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
    Around it3 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time

    Earlier incidents in the 14 days before

  • GitHub Incident with Git Operations, Pull Requests and Actions last seen 16:25 UTC unknown

    Posted 7 Oct 15:14 UTCUpdated 6d ago

    Git OperationsPull RequestsActions

    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%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded.GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers.Each outage ended when one of our established machines with correct confi…

    21 earlier updates
    1. 7 Oct 16:25 UTCResolvedOn October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across [GitHub.com](http://GitHub.com), including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a code fix was merged.We have completed a detailed root-cause review and are implementing improved database-health safeguards. We will continue to review and add additional safeguards to prevent future recurrence.
    2. 7 Oct 16:25 UTCResolvedThis 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.
    3. 7 Oct 16:23 UTCUpdateGit Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
    4. 7 Oct 15:58 UTCUpdateWe are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
    5. 7 Oct 15:56 UTCUpdateThe degradation has been mitigated. We are monitoring to ensure stability.
    6. 7 Oct 15:49 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
    7. 7 Oct 15:49 UTCUpdateThe degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
    8. 7 Oct 15:47 UTCUpdateThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
    9. 7 Oct 15:41 UTCUpdateWe are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
    10. 7 Oct 15:35 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
    11. 7 Oct 15:32 UTCUpdateActions is operating normally.
    12. 7 Oct 15:31 UTCUpdateThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
    13. 7 Oct 15:27 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
    14. 7 Oct 15:27 UTCUpdateGit Operations is operating normally.
    15. 7 Oct 15:25 UTCUpdatePull Requests is experiencing degraded performance. We are continuing to investigate.
    16. 7 Oct 15:24 UTCUpdateWe observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
    17. 7 Oct 15:21 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
    18. 7 Oct 15:16 UTCUpdateWebhooks is experiencing degraded availability. We are continuing to investigate.
    19. 7 Oct 15:15 UTCUpdateIssues is experiencing degraded performance. We are continuing to investigate.
    20. 7 Oct 15:14 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
    21. 7 Oct 15:14 UTCInvestigatingWe are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
    Around it3 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time

    Earlier incidents in the 14 days before

  • Cloudflare Cloudflare API service issues resolved 15:24 UTC 43 min

    Started 7 Oct 14:41 UTCUpdated 6d ago

    API

    This incident has been resolved.

    2 earlier updates
    1. 7 Oct 14:55 UTCMonitoringA fix has been implemented and we are monitoring the results.
    2. 7 Oct 14:41 UTCInvestigatingCloudflare is investigating issues with Cloudflare Dashboard APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
    Around it3 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time

    Earlier incidents in the 14 days before

Bars compare how long each incident lasted, up to three days; a lighter bar is a lower bound and a hatched one is unknown. Older incidents are kept for 90 days on the timeline.

Azure post-incident reviews

What went wrong in major incidents and what Microsoft is changing
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 14 Oct 13:56 UTC · 254 of 255 readable · 253 fully read · documentation 0/409 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.