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.

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

Thu 16 Jul1

  • Ubiquiti UniFi cloud Increased CloudFront 5xx Errors last seen 11:32 UTC unknown

    Posted 16 Jul 09:05 UTCUpdated 84d ago

    Ubiquiti UniFi

    The elevated 5xx errors affecting UI Cloud services have been resolved, and service has returned to normal operation.We will share additional information if further action or follow-up is required.

    1 earlier update
    1. 16 Jul 09:05 UTCInvestigatingWe are investigating elevated 5xx errors that may impact all UI Cloud services, including web portals, APIs, authentication, and cloud-managed applications.The issue appears to be related to an ongoing AWS CloudFront incident affecting customers using CloudFront VPC Origins. We are actively monitoring the situation, assessing the impact across our platform, and working with AWS as they investigate.We will provide updates as more information becomes available.

Yesterday9

Wed 7 Oct10

Tue 6 Oct17

Mon 5 Oct11

Fri 2 Oct6

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