Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 262/264 feeds/APIs · 418/442 docs · checked 20:00 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.

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.

Public status, not your tenant's health. Providers post only incidents they choose to share with everyone, usually wide ones. An empty list does not mean your services are healthy; for your own resources, check Service Health in the Azure portal or the Microsoft 365 admin center.

Right now

6 ongoing incidents at 3 providers

Operational, as stated:AzureAzure DevOpsMicrosoft 365 admin centerMicrosoft 365 and Copilot for consumersPower Platform admin centerAnthropic (Claude)Cisco MerakiUbiquiti UniFi cloudGitLab.com

No ongoing incident posted:Google Gemini and Vertex AI

Ongoing 6 incidents

OpenAI Identified

New Ad Accounts failing to provision admins

Posted today 19:36 UTCread 4 min ago

Ads ManagerAds API

We have identified that new ad accounts are failing to assign their creator admin. We are investigating the issue.

Around it5 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

OpenAI Identified

Degraded Performance of Dots on Enterprise

Posted today 18:59 UTCread 4 min ago

dots

Our teams have identified the issue and are actively implementing a mitigation. At this time the majority of impact is affecting enterprise customers.

2 changes ChangeIntel noticed
  1. today 19:07 UTC ChangeIntel noticed the text change
  2. today 19:02 UTC ChangeIntel noticed a new title; it was "Dot Message Failures"
Around it5 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Cloudflare Monitoring

Elevated error rates for Durable Objects in Western Europe

Started today 17:51 UTC · open 2 h 26 min+Updated 2 h 2 min agoread 4 min ago

Durable Objects

A fix has been implemented and we are monitoring the results.

1 earlier update
  1. today 17:51 UTCInvestigatingWe are investigating elevated error rates affecting Durable Objects in Western Europe. Customers may see errors when using Durable Objects and related services. We will post updates as we learn more.
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Cloudflare Monitoring

Delayed audit log delivery for WARP and Zero Trust services

Started today 17:32 UTC · open 2 h 44 min+Updated 2 h 31 min agoread 4 min ago

Audit LogsZero Trust

A fix has been implemented and we are monitoring the results.

1 earlier update
  1. today 17:32 UTCInvestigatingWe are investigating an issue affecting audit log delivery for WARP API. Audit logs for some customers may be delayed or not delivered, and some dependent services may also be affected. We have identified the cause as a capacity problem in a shared internal data pipeline in our PDX region. Mitigations are in place and the pipeline is partially recovered. We are continuing to monitor and work toward full recovery.
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Cloudflare Investigating

Network Error Log Processing Unavailable

Started today 16:30 UTC · open 3 h 46 min+Updated 14 min agoread 4 min ago

Logs

Partial service restored. Root cause investigation is currently underway.

1 earlier update
  1. today 16:30 UTCInvestigatingSince 20:19 UTC, new Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

Earlier incidents in the 14 days before

GitHub Investigating

Errors loading Issues, Pull Requests, and search results

Posted today 15:28 UTCUpdated 26 min agoread 4 min ago

Pull RequestsIssues

Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.

12 earlier updates
  1. today 19:04 UTCUpdateSome updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
  2. today 18:26 UTCUpdateThe other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
  3. today 17:43 UTCUpdateWe're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
  4. today 17:41 UTCUpdateActions, Issues, Packages and Pull Requests are operating normally.
  5. today 17:16 UTCUpdateWe're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. We're continuing to work towards full recovery and monitoring for stability.
  6. today 16:41 UTCUpdateSome users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. We're working through multiple mitigation efforts and continuing to investigate.
  7. today 16:35 UTCUpdateAPI Requests is operating normally.
  8. today 16:28 UTCUpdatePackages is experiencing degraded performance. We are continuing to investigate.
  9. today 16:26 UTCUpdateAPI Requests is experiencing degraded performance. We are continuing to investigate.
  10. today 16:08 UTCUpdateSome users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and evaluating mitigation options to restore normal service.
  11. today 15:33 UTCUpdateSome users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and working to restore normal service.
  12. today 15:28 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Issues and Pull Requests
Around it6 other incidents at the same time · 5 earlier incidents

Elsewhere at the same time

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 22 Oct 20:00 UTC · 262 of 264 readable · 260 fully read · documentation 418/442 current