Skip to main content

Is Royal Road Down?

No — Royal Road is up

Reachable from all 8 checked regions

Average response time: 709ms

Last checked · checks run every 6 hours

Official status page: https://status.royalroad.com

Royal Road uptime

95.96%
Last 7 days
98.05%
Last 30 days
98.05%
Last 90 days
536ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

2-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 16 checks
Aug 4: 100.00% uptime, 40 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 31 checks
Aug 7: 100.00% uptime, 31 checks
Aug 8: 100.00% uptime, 24 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 74.19% uptime, 31 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 40 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 96.88% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
398ms
DNS 0ms TCP 2ms TLS 6ms TTFB 275ms
fra
102ms
DNS 0ms TCP 2ms TLS 8ms TTFB 96ms
gru
600ms
DNS 0ms TCP 3ms TLS 9ms TTFB 422ms
iad
316ms
DNS 0ms TCP 1ms TLS 7ms TTFB 309ms
jnb
576ms
DNS 0ms TCP 0ms TLS 13ms TTFB 399ms
lax
406ms
DNS 0ms TCP 1ms TLS 8ms TTFB 400ms
lhr
133ms
DNS 1ms TCP 1ms TLS 9ms TTFB 104ms
nrt
3203ms
DNS 0ms TCP 1ms TLS 11ms TTFB 2809ms
ord
343ms
DNS 0ms TCP 1ms TLS 11ms TTFB 322ms

What Royal Road does

Royal Road is a web fiction platform where authors serialise novels chapter by chapter, mostly progression fantasy and LitRPG, and readers follow along through reading lists and notifications. Authors post on schedules their readers track closely, so an outage during a release window is noticed by a great many people at once.

What an outage looks like

Chapter pages return a Cloudflare error page rather than a Royal Road one, or the site loads while individual chapters fail to open. Posting a new chapter fails at the submit step. Reading lists and follow notifications stop updating. The mobile app fails to sign in or shows an empty library while the website works, since the app uses a separate API and auth server.

What to do about it

Check status.royalroad.com, which reports Website via Cloudflare and Website direct as separate components, alongside the mobile API, the auth server, the database and the load balancers, each with a response time and an uptime figure. That split is the useful part: if the direct check is up and the Cloudflare one is down, the problem sits in front of Royal Road. Draft chapters elsewhere before pasting them in.

Is it down for everyone, or just you?

If this page says Royal Road is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

W
Wattpad
Patreon
Patreon
Cloudflare
Cloudflare
Discord (for communities)
Discord (for communities)

Royal Road outage FAQ

Is Royal Road down, or is it a Cloudflare problem?
Royal Road's status page answers this directly, which few sites do. It measures the website through Cloudflare and the website directly as two separate components and says so on the page. If the direct component is operational and the Cloudflare one is not, the failure is in the layer in front of Royal Road, and nothing the site's own team does will clear it faster.
Will a chapter I was writing be lost?
Anything only in the browser editor is at risk, because a submit that fails during an outage can take the draft with it when the page reloads. Write or paste long chapters from a local document rather than composing in the browser during an incident. If a submit is hanging, copy the text out before touching refresh, which is the point where drafts usually disappear.
Why does the mobile app work when the website does not?
They run on different components. Royal Road tracks the mobile API and the auth server separately from the website, so the app can keep serving chapters while the site fails, or fail to sign you in while the site is fine. Trying both is worthwhile before concluding Royal Road is down, and which one works tells you roughly where the problem is.
Do I lose my reading progress during an outage?
Progress already recorded on your account stays. What may not survive is progress from the outage itself, since marking a chapter read is a write to the database and writes fail before reads do during most incidents. You may find a chapter you finished mid-outage is still marked unread afterwards, which is a display of what was saved rather than a bug.

How we measure this

  • We request Royal Road's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Royal Road publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Royal Road goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required