Status page served a one-cycle partial response from Cloudflare edge

At 00:00:01 UTC on 2026-04-20, the external status-page probe detected that status.gablvm.org returned a 200 response that did not contain the expected v3 template marker. The response cleared on the next probe cycle 10 minutes later with no intervention. No deploy happened in that window (the live Cloudflare Worker version did not change). Investigation identified the most likely cause as a transient Cloudflare edge bot-fight challenge triggered by the probe's fixed-IP 10-minute pattern. Mitigation applied: probe now sends an identifiable User-Agent and the server IP is whitelisted in Cloudflare's firewall. Site was never unreachable to real users during this window.

• Posted: Apr 20, 2026, 00:00 UTC
• Resolved: Apr 20, 2026, 00:35 UTC
• Duration: 35m

Timeline

1. resolved

   00:35 UTC

   All automated probes have reported healthy since the mitigations were applied. Public users were never affected — the only impact was a false-positive internal alert. The status page has been operating normally throughout.

2. monitoring

   00:30 UTC

   Two mitigations deployed: (1) the external probe now sends an identifiable User-Agent header, (2) the source server's IP address is added to Cloudflare's zone allowlist. Running 8 back-to-back manual probes confirmed the marker is present on every response. Monitoring the next few probe cycles for stability.

3. identified

   00:15 UTC

   Correlated the probe log with the Cloudflare Worker version history. The live Worker version did not change during the incident window. The response cleared on the very next 10-minute probe cycle with zero intervention, so this was not a deploy drift. Most likely cause is a transient Cloudflare edge event — the probe's fixed-IP 10-minute pattern can trip bot-fight heuristics briefly.

4. investigating

   00:00 UTC

   Tier 2 external probe detected that status.gablvm.org returned a 200 response missing the expected v3 template marker at 00:00:01 UTC. No code deploy happened in that window. Investigating whether this is a stale-bundle recurrence or an edge-level event.

Permalink: /incident/50