Browser spins.
Site won't load at all.
If the browser just hangs or shows a connection error (not a 404), the problem is usually DNS, a completely failed deploy, or the hosting provider has an outage.
Check these in 60 seconds
1. Try loading the site from your phone on cell data (not WiFi) — if it works, it's a local network or DNS issue on your machine. 2. Check githubstatus.com or your host's status page for outages.
Common causes & fixes
Check githubstatus.com. If GitHub has an incident, nothing to fix — wait for them to resolve it.
Run nslookup yourdomain.com. If it returns nothing or the wrong IP, your DNS records are broken or haven't propagated.
GitHub → Actions tab. If the last deploy shows a red X, the site may be in a broken state. Roll back with git revert HEAD --no-edit && git push.
Try a different network or flush your DNS: sudo dscacheutil -flushcache (Mac) or ipconfig /flushdns (Windows).
Diagnose DNS from terminal:
# Check if your domain resolves: nslookup yourdomain.com # Check if GitHub Pages IP is correct: nslookup yourdomain.com 8.8.8.8 # Flush local DNS (Mac): sudo dscacheutil -flushcache