← Back to Cloudflare History
minor✓ Resolved

Custom Hostname API issue

Cloudflare•Sun, May 31, 2026, 01:06 AM
Status
resolved
Duration
2d 17h
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedTue, Jun 2, 2026, 06:40 PM
This incident has been resolved.
monitoringTue, Jun 2, 2026, 01:16 AM
A fix has been implemented and we are monitoring the results.
identifiedMon, Jun 1, 2026, 12:47 AM
The issue has been identified .
investigatingMon, Jun 1, 2026, 12:34 AM
The previous fix was not sufficient and hence we are continuing to investigate this issue.
monitoringSun, May 31, 2026, 11:27 PM
A fix has been implemented and we are monitoring the results.
investigatingSun, May 31, 2026, 01:06 AM
Cloudflare is investigating increased latency for customers using the Cloudflare for SaaS Custom Hostname API. Customers may experience slow responses while adding a new R2 subscription. Existing Custom Hostnames remain unaffected and are operating normally.

📊 TECHNICAL DETAILS

Internal ID
0fe5173c-ec23-48bb-8886-8c61ea0c4020
External ID
59gsh0xrh6gg
🕐 Started
Sun, May 31, 2026, 01:06 AM
🔄 Last Updated
Tue, Jun 2, 2026, 06:40 PM
✓ Resolved
Tue, Jun 2, 2026, 06:40 PM
MINOR
Impact Level
2d 17h
Total Duration
5
Status Updates
Affected Components
SSL for SaaS Provisioning
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed