Cloudflare Status · History · Incident #4130
RESOLVEDCloudflare Notifications issues
Minor · Started May 29, 2026 · 7:32 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Cloudflare Status · History · Incident #4130
RESOLVEDMinor · Started May 29, 2026 · 7:32 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
Peak 1/hr
Summary
This incident has been resolved.
Started
May 29, 2026 · 7:32 AM
Resolved
May 29, 2026 · 7:32 AM
Duration
< 1m
Severity
Minor
Event timeline
Monitoring
May 29 · 7:32 AM CloudflareCloudflare is investigating issues with the Cloudflare Notifications product. Some alerts might be temporarily delayed. Impact is restricted to the notification functionality and it does not affect any connectivity, security, CDN or Area1 functionality. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Resolved
May 29 · 7:32 AM CloudflareThis incident has been resolved.
User reports · incident window
Hourly report count — red bars mark the incident window.
Peak: 1 reports/hr
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT