www.bbc.co.uk
Maybe yes + bad config in their servers. I am seeing CORS failure on their crapchallenge pages. Frankly, good thing very few sites in my country use them. (And AFAIK no eshop, CF's incompetency with their "protection" would be costly as is, with outages like this, it could be downright company-ending)
Wow, those two are biggies. I have another app or two which are having issues. Here now a company I wasn't aware of is responsible for 20% of internet traffic? That's still why I don't believe in keeping anything personal (like pictures or documents) in storage on the web, unless it's only a backup.
Apollohoax.net is down too. The webmaster there recently added a Cloudflare human authenticator to cut down on bot traffic.
Indeed. My friend runs an ISP that offers boutique hosting. It's where I host my Apollo website. Some of his customers have 15-minute SLA agreements. That means that the site he hosts for them can be unavailable for at most 15 minutes for pretty much any reason, after which he has to pay them $100 a minute until service is restored. When their service fails, it's an all-hands-on-deck exercise.
So no great loss then....About 20% of websites doen including X and Chat GPT
Cloudflare apologises for outage which took down X and ChatGPT
"We apologise to our customers and the Internet in general" the web infrastructure company said.
No loss at all that I can see. Has zero effect on any of my online activity.
I was going to give this one of those emoji/smiley reaction things, but I couldn't pick between 'ha ha' and 'wow', and what I really wanted was an 'oh, we're ◊◊◊◊◊◊', which we don't have (also: I'm not sure how that could be rendered in emoji form, not without giving poor Otto a stroke, anyway).
Worth it.
www.theregister.com
So incompetence then.It was not DNS this time. Nor BGP.
Cloudflare broke the internet with a bad DB query
: Thought it was the victim of a ‘hyper-scale DDoS attack’ before finding the fix
Isn't it always?
Hmmm, in my experience about 5-10% of technical issues are genuinely hardware induced, excluding hardware problems caused by human stupidity (wrong equipment, stretching cables at ankle height, turning off cooling, et cetera).
And, of course, NONE of those solutions include anything like "TEST ALL UPGRADES IN A CONTROLLED ENVIRONMENT BEFORE RELEASING THEM!!"
Maybe someone broke the lava lampsIt was not DNS this time. Nor BGP.
Cloudflare broke the internet with a bad DB query
: Thought it was the victim of a ‘hyper-scale DDoS attack’ before finding the fix
Why would they...
Yep. They do apologise but from the start it's as if the change to the database was a natural event that just happens.
