Thanks for asking! You guys are right, we should clarify what info is most useful to us, so I will do that now and ping everyone so they know. I apologize for not doing this sooner as I should've.

When there is a Cloudflare error, what helps us the most is knowing what specific page it occurred on. It is not necessary to copy-paste what the error says. Instead just include the following:

1. the error code (504 or 502)
2. what page you got it on
3. approximate time you got the error
4. how long the error lasted. (for instance, were you stuck on the 504 for the next half hour, or you wait 5 seconds, refresh, and it was back to normal?)

For example: "I got a 504 error on the page turning in the items for Pete's quests at 5:03 PM subeta time. The error went away after a single refresh."

This will help us identify if there are specific pages with inefficient/out-dated code we should take a look at. Generally if you only get the error once, and it goes away after a single refresh, it does not need to be reported. If you get the error on the same page more than once, please report it.

A few other things to note:

• Unfortunately it seems that, while we've mostly fixed the issue, servers going in and out of rotation can still increase the chance of 504 errors. Errors caused by this usually go away if you refresh the page, and don't need to be reported. Servers will move in rotation when 1) we make a deployment (check admin posts as I usually post when I personally deploy anything) and 2) when the number of people online jumps up or down rapidly and extra servers spin up/power down, usually at the beginning of holidays and events.
• This info applies to the Cloudflare error page, where the entire page turns into a big Cloudflare error. If you're just noticing a SQL error printed somewhere on a normal subeta page, check to see if it is the one explained in this topic and make a new topic if it's not.

Thank you! We are actually aware that the /friends.php page is notoriously laggy - the issue is worse the more friends you have. I will definitely look into updating that specific page.

That is unrelated to this topic. Please make a new topic or ticket about your problem.

I made a new topic for this so the information I wrote here (about what to include in the report, etc) doesn't get buried. Hopefully it will help you help us with your bug reports! :) I will lock this topic now.

Please use this topic from now on: Timeouts, Error Codes (5xx), Lag | FIRST POST UPDATED 7/22