Board Game Arena

+1 unable to file a bug report. I was surprised to see on the status page that there were no issues when you can see a massive drop in the games played stats from this. I get either weird timeouts or 504 gateway errors. folks in the general chat seem to think it's game-specific, so sharing the list of games I tried before giving up on playing anything for now:

- azul queen's garden
- race for the galaxy
- kingdomino
- carcassonne
- sapiens
- potion explosion
- azul
- flaming pyramids
- harmonies
- tacta

in the browser console I see a couple weird security errors
Security Error: Content at https://boardgamearena.com/forum may not load or link to file:///.
Security Error: Content at posting.php?mode=reply&t=51838&refresht ... heme=light may not load or link to file:///.

the 504 when creating tables appears to be from https://boardgamearena.com/account/account/setFp.html and when I look at the response in the network tab it's a basic nginx 504 page

Happening for me on

Pixies
Bizarre Manor
Isle of Cats

A couple hours ago it seemed to only affect some of my games, not all. But now I can’t get into any of my games.

It seems that x.boardgamearena.net is currently offline and causing all these problems

I can't believe that this has been an issue for over 4 hours now and not one email or message from BGA to explain what the issue is and when it will be resolved. This is not what I've paid my premium membership for and i won't be renewing.

Everything is working normally for me now.

For those who are feeling impatient, please remember that BGA is based in Europe and this happened in the middle of the night.

I DM'd BGA's FB page and the admin replied that things should be returning to normal soon.

This is the general forum. There's a subforum for every game not in alpha, if bug report problem still happens, post there instead

https://boardgamearena.com/forum/viewforum.php?f=1417

BGA needs to have a disaster recovering plan that includes standard communications protocols.

This would include posting regular updates on a system not associated with their server infrastructure (e.g. social media, website).

Once established, we would all know to visit that location and use it to understand the situation and dispel rumors.

The rule of thumb is to acknowledge, assess, and affect.

The first message during an outage would acknowledge the outage exists. Eventually the second message would affirm someone is investigating and assessing the issue. Any subsequent messages would provide a timeline around when the issue might be resolved.

Example: Around 6:37 pm Pacific last night there should have been the message: “Looks like BGA is down. We’ll investigate and update.”

The second message would have been: “We’ve got a team looking at the problem. We’ll assess and try to provide a timeline for fixing things.”

The third message would have been: “We think we see the issue, and we are working to have things fixed within the next two hours.”

Any subsequent messaging would be to amend that timeline.

Otherwise, your last message would have been: “We’ve resolved the issue!”

Example: Around 6:37 pm Pacific last night there should have been the message: “Looks like BGA is down. We’ll investigate and update.”

The second message would have been: “We’ve got a team looking at the problem. We’ll assess and try to provide a timeline for fixing things.”

The third message would have been: “We think we see the issue, and we are working to have things fixed within the next two hours.”

Any subsequent messaging would be to amend that timeline.

Otherwise, your last message would have been: “We’ve resolved the issue!”

6 pm pacific is 3 am in France. You want them to have a whole team of people sitting around all night every night just on the off chance that the site might fall over?