ZipRecruiter

False positive — probe-configuration issue, not a site outage. All 4 probe checks returned HTTP 421 (misdirected request) from the primary location (20:28, 23:06 UTC Oct 30; 01:43, 03:52 UTC Oct 31), a fast edge rejection, not a timeout or 5xx. Independent direct checks with a browser user-agent on 2026-10-31 ~09:10 PKT returned HTTP 200 with the full ZipRecruiter homepage twice. Same signature as incident #343 for this service, which was also resolved as a false positive on 2026-10-30; every probe of ZipRecruiter returns 421, so the probe configuration needs review to stop repeat false alarms.

False positive: probe returned HTTP 421 (misdirected request, http_client_error) on both checks, a fast edge rejection, not a timeout or 5xx. Direct independent checks from this VM with a browser user-agent returned HTTP 200 twice with the full ZipRecruiter homepage. Site is operational for real visitors; the probe itself is being rejected by the edge. Note: both probes in 30 days returned 421, so the probe configuration may need review to stop repeat false alarms.