Correlate browser connection resets with independent probes and exact edge requests

A browser connection-reset screenshot and an origin ECONNRESET line do not establish the same failing connection. Correlate the exact route, UTC failure time and request identity before assigning the cause to the database, origin, CDN or client network. When application logs are being dropped, their absence is weak negative evidence; use independent external probe history and edge request completion records. Successful health probes and successful page requests narrow a broad-outage hypothesis, but cannot exclude a sub-minute or regional connection failure, nor prove that response bytes reached the browser.

Applies to intermittent multi-user web failures behind a CDN with incomplete application telemetry. A useful next discriminating test is the same failing browser/request over the normal network and an alternate connection, with timestamped network evidence. Avoid restarting a healthy origin solely because unrelated reset lines exist.