I'm trying to get my fist campaign in 7 years up and going. because of friends and family being out to sea and conflict of schedule. FInally get everything ready and everyone on digital chat and video. Just to be hit with the roll one error. To make it worse. My Brother Has to ship back out again tomorrow so will have to basically start over and wait for more shore Leave. This is just not right.

We are currently experiencing widespread issues. The team is working hard to resolve this issue!

We are merging all related reports to this thread.

You can use the top right "Tools" option to subscribe to this thread for updates, or follow D&D Beyond on Twitter where we will post as soon as anything changes.

The team does not need users to share their unique error codes at this time.

Thank you very much for your patience!

feb7f4a87d90437db7dc9552c1a3e38d

I get this error code when I try to view one of my characters.

Quote from Vii007 >>

@DZenns38

It is annoying, true. But your anger isn't going to solve the problem any faster. Also while I will not try to imply that your rage is impotent in anyway, I've been a paid member for quite sometime and this is the first problem of this kind that the site has suffered while I've been using it. Most of the time the site is fantastic for game and making characters. Plus they've already assured us that they don't think this is a hack. However, if you really want a refund I'm sure their customer support would be more than happy to speak with you.

Just a head's up - this may be the first time you've encountered the issue while visiting the site, but in the 3-4 months I've been a subscriber, this is the third time DURING a session that it's gone out for me. Though, granted, this is by far the longest of the three (to my knowledge).

Going on record that I can't access character sheets which have features I paid for.  Is it possible to get a time estimate?

Thanks, I would appreciate the accountability. (Re: Ammja's last message)

A hit to availability, especially on the weekend, with a core feature of this type of service platform seems to me like near worst case scenario. I managed to get access to my sheet for a few minutes about 1-2 hours ago before losing it again. So at least I can be reasonably assured the information itself hasn't been lost.

I'm sure they already plan on it, but on the off chance: after resolution, it might be a good time to take a look at change management, redundancy, and recovery policies/procedures for mission critical functions.

From a business continuity perspective: I'd be interested in the post-mortem coming out of this. I know I'll be making sure to export a pdf from now on (a feature I didn't even know about until today). If just to make sure myself and the rest of the party are covered so we can keep playing our game. Things happen, but every event should come with some follow on changes, hopefully this spurs some in DND Beyonds operations as well.

It has been several months since our group has been able to get together and play and now that we are all here and ready to play, we can't load our character sheets. it won't work on any device. please fix as soon as possible!

I keep getting the same error code (8e9f935a0e4949359e6b43509e4d7756) and I can't gain access to any of my characters which I kinda need as my one-shot character is on here.

*plays sad violin music for bardic inspiration.*

Everytime I click 'basic' to start making a new character I get the 497a0a0f7389428aa28f9282230a65a4 error code and the beholder.

Same issue as Steward098 (error code eda727b8677b4c3b9c2ed34b4a08089c). Can't access my characters, because of an authentication issue.

Throw a coin to your IT team.

who got cheeto dust in the server again?

I am currently experiencing the following error code when accessing my character sheet: 8146a50d54c64de7a5f2ada56a5285d8  

Any updates or progress?? 

Same whole gaming group having issues here.  Code : d8393e2b66844336be71296018622149

I'm also receiving a error when I try to access any of my characters.  The error code is different that ones mentioned previously in this thread, however. Here's what it says:

did you try turning it off and back on again?