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 03:09 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

60 incidents · newest first

Today2

  • Cloudflare Cloudflare Workers - Cron Trigger Activation Issues resolved 01:29 UTC 19 h 53 min

    Started 14 Oct 05:36 UTCUpdated 2 h 22 min ago

    Workers

    Workers Cron Trigger backlogs have cleared and appear healthy. Cron Trigger schedules should be executing as expected. Some schedule redeploys may be required for a small fraction of Workers who were impacted during the incident.

    3 earlier updates
    1. 14 Oct 08:14 UTCMonitoringWe are continuing to monitor for any further issues.
    2. 14 Oct 07:23 UTCIdentifiedA fix has been identified and is underway
    3. 14 Oct 05:36 UTCInvestigatingCloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
    Around it6 other incidents at the same time · 5 earlier incidents

    Elsewhere at the same time · within 12 hours of its start

    Earlier incidents in the 14 days before

  • Palo Alto Networks cloud services AI Runtime Security (AIRS) Cloud Degraded Performance (AIRS API Intercept URL Filtering) in US last seen 01:26 UTC unknown

    Posted today 00:51 UTCUpdated 2 h 26 min ago

    United States - AmericasUnited StatesAI Runtime Security Cloud

    The issue affecting the URL Filtering Detection Service in AI Runtime Security API has been resolved. URL filtering detection features has worked normally since 01:07 UTC.Customer Impact: From about 00:00 UTC to 01:07 UTC on October 15, 2026, URL content in prompts and responses may not have been categorized or blocked. Scan requests kept processing and returned successful responses, and all other detections worked as normal. Other regions were not affected.We apologize for the inconvenience and will review how to prevent this from happening again.

    1 earlier update
    1. today 00:51 UTCInvestigatingWe are currently investigating this issue with URL Filtering Detection Service, that affects detection features offered by AI Runtime Security API.Customer Impact: Scan requests are still being processed and return successful responses, and all other detections work as normal. But URL content in prompts and responses may not be categorized or blocked while this lasts. Other regions are not affected.We'll post another update within 60 minutes, or sooner once service is restored.
    Around it4 other incidents at the same time · 1 earlier incident · 1 change in the 14 days before

    Elsewhere at the same time

    Earlier incidents in the 14 days before

    Changed in the 14 days before

Yesterday14

Tue 13 Oct22

Mon 12 Oct7

Sat 10 Oct2

Fri 9 Oct5

Thu 8 Oct8

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 15 Oct 03:09 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.