UpOrNot says a website appears to be unavailable. What now? The right next step depends on whether you're a visitor or the person responsible for the site.
If you're a visitor
- Wait a few minutes and check again. Most outages are short: deployments, restarts and traffic spikes often resolve on their own.
- Look for an official status page. Many services publish one at addresses like
status.example.com. - Check the company's social accounts for announcements about maintenance or incidents.
- Use an alternative if you need something urgently — a mobile app, a mirror or a different service.
If UpOrNot says the site is online but it still fails for you, the issue is probably on your side. See why a website can be online but not work for you.
If it's your website
1. Confirm the scope
Check from two networks and with UpOrNot. If our two probes both fail to connect, the outage is very likely real and global rather than a local glitch.
2. Read the failure reason
| Reason shown | Where to look first |
|---|---|
| Domain doesn't resolve | Domain expiry, registrar settings, DNS records (A/AAAA/CNAME) |
| Connection refused | Web server stopped, firewall, wrong port |
| Secure connection failed | Expired or misconfigured SSL/TLS certificate |
| Timeout | Overloaded server, network issues at your host, DDoS |
| 5xx server error | Application logs, database, recent deployment |
3. Communicate
Post a short, honest update on your status page or social accounts. Users forgive outages much more easily than silence.
4. Prevent the next one
- Turn on auto-renew for your domain and certificates.
- Keep a rollback plan for deployments.
- Set up continuous monitoring with alerts so you hear about problems before your users do.
Check a website now
Check statusFind out in seconds whether a site is down for everyone.