Skip to main content

Is D&D Beyond Down?

No — D&D Beyond is up

Reachable from all 8 checked regions

Average response time: 2156ms

Last checked · checks run every 6 hours

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

D&D Beyond uptime

99.55%
Last 7 days
99.50%
Last 30 days
99.50%
Last 90 days
1620ms
Avg response, 30 days

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

30-day history

3-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: no data
Aug 4: no data
Aug 5: 100.00% uptime, 16 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 96.88% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 97.50% uptime, 40 checks
Aug 15: 100.00% 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.

ams
1072ms
DNS 13ms TCP 1ms TLS 2ms TTFB 568ms
arn
1182ms
DNS 68ms TCP 2ms TLS 3ms TTFB 442ms
bom
9416ms
DNS 4ms TCP 1ms TLS 5ms TTFB 2068ms
cdg
1151ms
DNS 26ms TCP 1ms TLS 4ms TTFB 697ms
dfw
348ms
DNS 43ms TCP 1ms TLS 3ms TTFB 255ms
ewr
470ms
DNS 38ms TCP 1ms TLS 3ms TTFB 401ms
sjc
1092ms
DNS 4ms TCP 0ms TLS 3ms TTFB 674ms
syd
3171ms
DNS 7ms TCP 0ms TLS 3ms TTFB 1470ms
yyz
445ms
DNS 19ms TCP 0ms TLS 3ms TTFB 286ms

What D&D Beyond does

D&D Beyond holds character sheets, rulebooks and campaign material for Dungeons & Dragons players, and most groups reach for it mid-session rather than between them. Its status page separates the character builder, character sheets, campaigns, the Maps and Sigil virtual tabletops, the encounter builder, homebrew, the compendium, the marketplace, the mobile app and the Avrae Discord bot.

What an outage looks like

Character sheets load without their content, or show stale values and refuse to save a hit point change. The compendium returns empty search results while the rest of the site works, since game listings are their own component. Maps and Sigil sessions drop players mid-encounter. The Avrae bot stops answering roll commands in Discord even though Discord itself is fine, which is often the first thing a table notices.

What to do about it

Check status.dndbeyond.com, which lists the character sheet, character builder, campaigns, Maps VTT, Sigil 3D VTT, the compendium, homebrew, forums, the marketplace, subscriptions and the Avrae bot separately, so a sheet problem and a marketplace problem read differently. For a session underway, the mobile app caches recently opened sheets and often keeps working when the website does not. Avoid re-entering a purchase that appeared to fail.

Is it down for everyone, or just you?

If this page says D&D Beyond 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

Discord (for communities)
Discord (for communities)
R
Riot Games
P
PlayStation Network
Patreon
Patreon

D&D Beyond outage FAQ

Can I still play if D&D Beyond is down?
Usually yes, with preparation that takes a minute. The mobile app holds recently opened character sheets offline, so a sheet you loaded before the session generally stays readable. Beyond that, a screenshot or PDF export of each sheet kept in the group chat covers the case where nothing loads at all. Dice and rules can be handled at the table; the sheet is the part that is genuinely hard to reconstruct from memory.
Will I lose changes I made to my character?
Edits that were saved before the incident are stored server-side and come back with the service. The risk is a change made during a partial outage, where the sheet renders but the save request fails: the value looks updated in the browser and is not actually recorded. If you edited anything while the site was misbehaving, re-open the sheet after recovery and confirm the change stuck before continuing.
Why has the Avrae Discord bot stopped responding?
Avrae is listed as its own component on the status page, and it depends on D&D Beyond for character data. It can therefore go quiet while Discord is entirely healthy, which is why the failure looks like a Discord problem to the table. If Avrae is silent but sheets load in a browser, the bot itself is the affected component and rolling physical dice is the practical workaround for the session.
Does an outage affect content I already purchased?
Purchased books stay attached to your account; an outage affects reaching them, not owning them. The marketplace and subscriptions are separate components from the compendium, so buying can fail while reading works, or the reverse. If a purchase appeared to fail, check your account after recovery before buying again, because a charge that went through with a failed page response is easier to spot than to reverse.
Is it down for everyone or just my group?
The measurement above checks from several regions, which distinguishes a real outage from a local network or account problem. If our probes are green and the status page reports nothing, have one player try on mobile data rather than the shared home or venue network. A single player failing while the rest of the table works is nearly always a client-side or connectivity issue rather than a service incident.

How we measure this

  • We request D&D Beyond'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 D&D Beyond 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 D&D Beyond 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