Troubleshooting an unreachable website
Check DNS, connectivity, protocols and service status from light to heavy, then verify any change.
Updated · Egress Observatory
Start with symptoms and scope
Determine whether one website, a service category or all websites are affected. Record the time and network; changing several settings at once obscures which one mattered.
Guided diagnosis combines observations into a next step. Possible causes are inferences; browser restrictions, server rejection and connection failures can produce similar errors.
Check one layer at a time
Start with official service status and a light request, then DNS answers, expected routing and IPv4/IPv6. A server-side domain failure does not establish a failure on the user connection.
Run stream, speed or multi-region tests only when needed. Save before-and-after runs and compare matching sources and measurement points; missing items do not count as success.