Agree with above - Cloudflare says it IS your fault. I mean, maybe they're wrong? But that's what the error page says.

If it's a cloudflare problem, why is the error telling me the problem is with the host, and not with cloudflare? is confuzzled

Same as Paddy here. Cloudflare server in Paris is all green. States problem is indeed with subeta.net as host... :(

Hello Staff? This is unbearable. Esp. since some could play earlier this morning and most likely later tonight - we are all in different time zones and hunting for our points/XP/whathaveyou.

Same happening over here, it's annoying. I need to play all the games for the event from today, but I'm simply not able to play them because of all the errors, when I do manage to get a game to load, then at the end there are issues again so my score isn't send in and I don't get credit for them Collected all of the points until now and I don't want to miss out on points for something like this :( Please fix this

I'm getting the same error- it's not cloudflare, it's the host.....

Except that all 502 and Bad Gateway errors really are on CloudFlare's end though... not Subetas.

Not saying both sides aren't passing the buck, but I would love it if it could be figured out who's end the problem is really on, so that the correct person can be fixing the correct problem. It's unbearable when it's every other click, and certainly makes me glad I didn't buy the GA I was actually thinking about again. As someone who stopped donating a while back.

The example of 500 series errors that are on their end on their website are completely different, and no other CloudFlare utilizing site is giving me issues, as usually happens when it's a CloudFlare issue (and one of the sites I'm counting in that is also very very small, so it's not that either).

Totally precious how Subeta is essentially unusable this afternoon. I don't care what side the error is on, but if this is an issue with Cloudfare that other sites have ditched the server for... perhaps Subeta needs to like,... upgrade to better servers. Again.

That you're not having issues on other sites means nothing. Really. They might not use the same servers even though it's the same host.

502 is an error that occurs between servers when they communicate with each other. Subeta pays for server space, they can't fix the actual server when it acts up.

Seems to be fixed now knock on wood, thank you!

Its working for me now. :)

I get how it CAN mean nothing, but I am saying in this particular instance, Cloudflare was having issues on their end about 12-15 hours ago, and it was affecting many sites (imgur, a blog I read, etc). They resolved those issues, and it still persists for Subeta. It's also a completely different error (that error page is from Cloudflare's server, so it IS being accessed).

Cloudflare also says the problem is on Subeta's hosting's end. Cloudflare doesn't host the whole site, and while Subeta doesn't have direct control over any/all of it's servers, no, they could be from a different company that it is still on Subeta's end to fix.

Regardless, both sides just going "They need to fix it" and neither actually fixing anything does 0 good.

Thank you. And of course no one has bothered to address this issue yet today.

Another site tried using CloudFlare. They found it sucked. They got rid of it. They also told users that CloudFlare sucked. I think that's because that site isn't run by someone who'd rather show the world how omglolfaaaabulous he is when he's drunk and living at home than work on the actual issues the site's having.

When's that recode coming?

Not like that'll fix anything.

Whose fault is it exactly, ?

facepalm Bitching about whose fault the errors are and flat-out fucking insulting people are going to fix even less than just shutting up and waiting for them to be resolved. There's no reason to be as rude as some people have been here just because there are some error pages coming up.

Besides: news flash, when this announcement was posted, the pages were showing that it was a Cloudflare issue. It had changed to saying it was a Subeta issue in the meantime, and the fact that there was no new comment made on it since then doesn't mean they're not still working on fixing it jfc

I don't think people are realizing that when this announcement was made Cloudflare was the one who had the error. The page even said so but today it's changed and so the issue is now with subeta and not cloudflare

Cloudflare is used on some of the largest sites on the internet (imgur, digg, etc) so it's not like we're using some small service that crashes all the time and just deciding to stick with it out of some insane reason.

Beyond that, the error was with cloudflare for the entire day that we posted this announcement. Since then we've had additional server issues outside of the cloudflare problems (which I've posted about on other threads) and are working quickly to solve those problems. Unfortunately, it's the weekend. That means that our ability to add new servers to our database cluster (and other things that require someone outside of Subeta doing work) is hindered by standard working hours. This isn't a case of us not doing anything (we've got multiple new servers spun up waiting to be added to the database cluster) but a situation where we have limited control over various parts of our server setup.

I never said CloudFlare was some small service, but, yeah, it does go down a lot. It and Subeta in general. There's always a "reason", too. How about higher more programmers and instead of putting the effort into pushing out, erm, "reference" items that Subeta's selling for personal profit, maybe try to speed up that recode that's supposed to magically fix everything that's been hinted at and promised for at LEAST a year?

I do hope the money the site's been making from users is going towards that and not frivolous things. :)

This is happening an extreme amount to me tonight, I had hoped it had been resolved :(