← All status codes
523

Origin Unreachable

Cloudflare-specific. Cloudflare can't find a network route to your origin server.

This happens lower down than 521 or 522. Cloudflare wasn't refused or ignored. It couldn't reach the origin's IP address at all.

What we see on Larm

Failed HTTP checks on Larm from 9 October to 8 November 2026, across about 130 monitors.

One monitor got a 523 in this period, a single failed check with a time to first byte of 7.4 seconds.

COMMON CAUSES

The origin IP in Cloudflare DNS is wrong or out of date, for example after a server move
A routing problem between Cloudflare and your host
In AWS, a broad VPC route, like 172.0.0.0/8, that captures traffic meant for Cloudflare

HOW TO FIX IT

Check the A and AAAA records in Cloudflare
Ask your host for a traceroute or MTR from the origin to a Cloudflare IP
In AWS, add a more specific route for 172.64.0.0/13 to your internet gateway

What this means for monitoring

If you've just moved servers or your host changed your IP address, check DNS first.

Related status codes

5xx Server Error

Get alerted when your endpoints return unexpected status codes.

Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.