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 18: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.

Ended in the last 7 days

59 incidents · newest first

Today1

  • Cisco Meraki Cloud Communication Interruption last seen 17:10 UTC unknown

    Posted today 13:58 UTCUpdated 1 h 39 min ago

    North and South AmericaDashboardEnd User Device Connectivity

    This incident is now resolved. We are sorry for any interruption to your service.

    3 earlier updates
    1. today 16:26 UTCMonitoringWe have deployed a fix and regular service is now restored. We will continue to monitor the situation. Please reach out to Meraki Support if you a re still experiencing a service interruption.
    2. today 14:15 UTCIdentifiedWe have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.
    3. today 13:58 UTCInvestigatingWe are investigating an issue with the Device to Cloud Communication that is impacting some users. Next update as soon as more information becomes available.
    Around it6 other incidents at the same time · 1 change in the 14 days before

    Elsewhere at the same time

    Changed 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 18:00 UTC · 254 of 255 readable · 253 fully read · documentation 0/409 current