Resolved Cloudflare · degraded service

OBS API availability

Started today 03:48 UTC, resolved today 04:12 UTC: it lasted 24 min.

Cloudflare status page On the status board

24 min How long it lasted, from the provider's times

1Update posted

5Other incidents at the same time

What it affected

As the provider names it

Observatory

What the provider posted

Newest first

today 04:12 UTCResolvedFor about 30 minutes there was reduced availability for customers using the OBS API. This has been identified, and we are back to normal for now.

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Elsewhere at the same time

Cloudflare Audit Logs v2 ingestion is missing multiple Cloudflare products
GitLab.com Increase of HTTP 50X errors on GitLab.com
Cloudflare Elevated Errors in China Network Colos
Cloudflare Possible Network Congestion in Dallas, TX, United States (DFW)
Cloudflare Cloudflare One Clients are incorrectly challenged on some sites

Earlier incidents in the 14 days before

Cloudflare: Possible Network Congestion in Dallas, TX, United States (DFW)Service incident · 14 Oct
Cloudflare: Network Performance Issues in LAXService incident · 13 Oct
Cloudflare: Cloudflare Service IssuesService incident · 13 Oct
Cloudflare: Cloudflare Workers - Cron Trigger Activation IssuesService incident · 2 times, latest 13 Oct
Cloudflare: Network performance issues in Ashburn, US (IAD)Service incident · 13 Oct

What changed

First observed 14 Oct 2026

No field changes in the recorded history.

Cite this recorded revision to keep the same title, summary, facts and links when the page changes.

A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.

Keep track

Service status now: every provider ChangeIntel reads, with ongoing incidents first.
Status RSS feed: new and ended incidents as they happen.
Everything about Cloudflare: its changes, known issues and incidents on one timeline.