What this can tell you

Results show whether a few public application resources answered this browser. The Homepage check uses HEAD to inspect response headers; it does not download or render the full Dashboard HTML. These checks cannot identify the failing network layer, prove a root cause, or diagnose a failure that prevented this HTML page from arriving. Failure origin is therefore reported as UNKNOWN.

Browser checks

One run makes at most four sequential requests and stops after 8 seconds.

Diagnostic script has not loaded yet. If this message remains, a page asset may have failed to load.

Loading diagnostic request results
Check Status Time Application request ID Probe correlation
Homepage headers Not run — — —
Build version Not run — — —
Application health Not run — — —
Dashboard asset Not run — — —
UTC
—
Reported build revision
—
Failure origin
—
Return to Dashboard

The report contains only UTC time, fixed same-origin paths, methods, response status, timings, application request IDs, the reported build revision and coarse build metadata, a random per-request diagnostic nonce, the allowlisted probe-correlation response headers, and a coarse result. It excludes query strings, user IDs, cookies, credentials, response bodies, and all other headers.