HTTP 530 is not a standard status code. Cloudflare uses it when it can't get to your origin server, and it always comes with a more specific 1xxx error on the error page. That number tells you what went wrong:
| Shown on the page | What it means | Jump to |
|---|---|---|
| Error 1016: Origin DNS error | Cloudflare can't find the IP address of your origin | Section 1 |
| Error 1033: Argo Tunnel error | Your Cloudflare Tunnel isn't connected | Section 2 |
| Another 1xxx number | A different configuration problem | Section 3 |
If you're a visitor, not the site owner, there's nothing to fix on your side: the site's server or DNS setup has a problem, and only its owner can solve it. Try again later.
1. Error 1016: origin DNS error
Cloudflare looks up your origin's address using the DNS records in your Cloudflare dashboard. Error 1016 means that lookup failed.
Check the record for the hostname that fails (Cloudflare dashboard, DNS, Records):
- A or AAAA record: does it point to the right IP address? If your server's IP changed (a new VPS, a rebuilt instance), update it.
- CNAME record: does its target still exist? Check it from any computer:
dig +short app.example-host.com
If that prints nothing, the target hostname no longer resolves. This is common when:
- an app on a hosting platform (Heroku, Render, Vercel, a load balancer) was deleted or renamed, so the CNAME points at nothing;
- a custom domain was removed from that platform;
- a typo crept into the CNAME target.
Fix: point the record at a hostname or IP that resolves, or recreate the app or custom domain on the hosting platform. DNS changes in Cloudflare apply within a minute or two.
Also check: if the record exists but the origin is reached through another domain, make sure that domain itself hasn't expired. An expired domain stops resolving, and every CNAME pointing at it fails with 1016.
2. Error 1033: Cloudflare Tunnel isn't connected
If your site is published through Cloudflare Tunnel (cloudflared), Cloudflare returns 530 with Error 1033 when no tunnel connector is running.
On the server that runs the tunnel:
# Is the service running?
sudo systemctl status cloudflared
# Which tunnels exist, and do they have active connections?
cloudflared tunnel list
cloudflared tunnel info <tunnel-name>
Common causes and fixes:
| Cause | Fix |
|---|---|
cloudflared stopped or crashed | sudo systemctl restart cloudflared, then check journalctl -u cloudflared -n 50 for the reason |
| Server rebooted and the service wasn't enabled | sudo systemctl enable cloudflared |
| The tunnel was deleted or its credentials changed | Recreate the tunnel or reinstall the connector with the new token |
| The DNS record points at an old tunnel ID | Make sure the CNAME target is <tunnel-id>.cfargotunnel.com for the tunnel that's running |
| The server can't reach Cloudflare (outbound firewall) | Allow outbound connections from cloudflared (it connects out; no inbound ports are needed) |
If cloudflared runs but your app behind it is down, the error usually changes to a 502 instead, so 1033 points at the tunnel itself.
3. Other 1xxx errors with 530
If the error page shows a different number, look it up in Cloudflare's own error documentation by that number: each one has its own cause. The DNS records and the tunnel are still the first two places to check, because they're where most 530 errors come from.
4. How 530 differs from other Cloudflare errors
| Error | What failed |
|---|---|
| 530 (with 1016 or 1033) | Cloudflare can't find or reach the origin at all (DNS or tunnel) |
| 521 | The origin refused the connection (web server down, or firewall blocking Cloudflare) |
| 522 | The connection to the origin timed out |
| 523 | The origin is unreachable on the network |
| 524 | The origin connected but took too long to respond |
| 525 / 526 | SSL handshake or certificate problem between Cloudflare and the origin |
For the 52x errors, see Cloudflare 52x errors: troubleshooting.
5. Know when it happens
A 530 usually starts after a change: a DNS edit, a deleted app, a server rebuild or a tunnel that didn't come back after a reboot. Every visitor gets the Cloudflare error page until someone notices.
With Pingzo, an HTTP monitor checks your public URL through Cloudflare every 1 to 15 minutes depending on your plan. A 530 counts as a failed check, an incident opens when 3 of the last 5 checks fail, and alerts go to WhatsApp, Slack, Telegram, Discord or email. Pingzo's paid plans also warn you before a domain expires and when DNS records change.
Related guides
- Cloudflare 52x errors: troubleshooting
- Could not resolve hostname: nodename nor servname provided (fix)
- HTTP 4xx and 5xx error codes explained
Stop Finding Out About Outages from Angry Users
Get instant WhatsApp & Discord alerts the second your API, website, or server goes down. Setup in 30 seconds, with checks as often as every minute.