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: 215/216 feeds/APIs · 387/387 docs · synced 01:36 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

53 incidents · newest first

Wed 7 Oct2

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

    Posted 7 Oct 17:17 UTCUpdated 31 h 54 min ago

    Git OperationsPull RequestsActionsIssues

    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.

    5 earlier updates
    1. 7 Oct 18:00 UTCUpdateAll systems have recovered. We have applied mitigations and do not anticipate another recurrence.
    2. 7 Oct 17:27 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
    3. 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.
    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 shortly.
    5. 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 33 h 33 min ago

    Git OperationsPull RequestsActions

    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.

    19 earlier updates
    1. 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.
    2. 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.
    3. 7 Oct 15:56 UTCUpdateThe degradation has been mitigated. We are monitoring to ensure stability.
    4. 7 Oct 15:49 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
    5. 7 Oct 15:49 UTCUpdateThe degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
    6. 7 Oct 15:47 UTCUpdateThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
    7. 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.
    8. 7 Oct 15:35 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
    9. 7 Oct 15:32 UTCUpdateActions is operating normally.
    10. 7 Oct 15:31 UTCUpdateThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
    11. 7 Oct 15:27 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
    12. 7 Oct 15:27 UTCUpdateGit Operations is operating normally.
    13. 7 Oct 15:25 UTCUpdatePull Requests is experiencing degraded performance. We are continuing to investigate.
    14. 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.
    15. 7 Oct 15:21 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
    16. 7 Oct 15:16 UTCUpdateWebhooks is experiencing degraded availability. We are continuing to investigate.
    17. 7 Oct 15:15 UTCUpdateIssues is experiencing degraded performance. We are continuing to investigate.
    18. 7 Oct 15:14 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
    19. 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

Tue 6 Oct2

Mon 5 Oct1

  • GitHub Incident with Actions last seen 22:49 UTC unknown

    Posted 5 Oct 19:11 UTCUpdated 3d ago

    Actions

    On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.

    12 earlier updates
    1. 5 Oct 22:49 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. 5 Oct 22:40 UTCUpdatePages is operating normally.
    3. 5 Oct 21:54 UTCUpdateActions is operating normally.
    4. 5 Oct 21:32 UTCUpdateWe have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
    5. 5 Oct 21:31 UTCUpdateActions is experiencing degraded performance. We are continuing to investigate.
    6. 5 Oct 21:22 UTCUpdatePages is experiencing degraded performance. We are continuing to investigate.
    7. 5 Oct 21:09 UTCUpdateIn addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
    8. 5 Oct 20:47 UTCUpdateActions is experiencing degraded availability. We are continuing to investigate.
    9. 5 Oct 20:39 UTCUpdateWe’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
    10. 5 Oct 19:50 UTCUpdateWe’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
    11. 5 Oct 19:15 UTCUpdateWe’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
    12. 5 Oct 19:11 UTCInvestigatingWe are investigating reports of degraded performance for Actions
    Around it5 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 9 Oct 01:36 UTC · 215 of 216 readable · documentation 387/387 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.