Further increase confusion by having error pages where all 3 are green
That’s user error. “Everything is working fine on our end. You figure it out, champs”.
I’m pretty sure I’ve had to debug errors like that
When you’ve eliminated all other possibilities, it must be the user that’s at fault
Well, that is an available preset too: https://virt.moe/cferr/wxqcqcd
I think that’s the first time I’ve seen the .moe TLD outside catbox. What even is it, I just think of the bartender from the Simpsons.
It’s for things that are moe
I did look it up after posting, and thought this one explained it better:
https://nic.moe/en/What is moe?
The word “moe” (in Japanese: “萌え”; pronounced as “moh-ay”) is a slang word rooted deep in the Japanese Otaku culture. It has often been used to mean a particular type of “adorable” or “cute” towards fictional characters, people, animals, etc.
Oh, man, the people that design most REST APIs got loose!
Add a contact button so they can email CloudFlare about the bug directly.
Add more colours a button that turns it into a slot machine. Three sevens and you win a prize.
(a redirect to a picture of a duck)
Any body could just go to down detector. And of course effectively check the status of cloud flare based on if downdetector shows this page themselves.
If its a cloudfront IP block down detector wont do you any good. Complaining to cloudfront wont do you any good either…
Ooo that’s fun. Might have to add that to my site.
derrick from sales guy vs web dude would have loved this
And it results in a call to the ISP’s customer service for 30 minutes.
I would forget I set this up and not fix the problem for a while. Honestly seems like a win if the boss can’t tell.
Flip the script
Ohhh i’m adding that
We need a fourth one for “User error”.
A pebkac mode.
“You’re doing it wrong ya doofus”
Probably better off simulating the impression without the company name on display.
This is peak SRE: better UX, better telemetry, and better blame routing—all in one error page.
Lmao shit dude that’s like something out of an 80s corporate disinformation campaign.
Beautiful.
A cloudfront ip block would be even simpler to do.
That’s gotta be like actually illegal unless cloud flair is to blame and then how did they reach your server?
Just call it cloudfare.
douclflare
text-spacing: -0.2em;letter-spacing*
Honestly, unless I see the correct version, my brain defaults to this name as the correct one.
I mean, you have to modify it of course. You can’t literally blame cloudflare.
But you can modify everything so that it’s a funny joke that still looks like the cloudflare error that people know.
It’s almost certainly against cloudflares tos, and against the open source license terms for the website, so if cloudflare gets wind about you doing this, they can probably send you a cease and desist, and then cancel your contract with them.
If they’re really pissed, and you run a decently large site that regularly runs into errors, they might be able to successfully argue slander in court.
It’s trademark infringement.
Yeah, at this point Cloudflare should just trademark network outages.
You know Amazon would try to crash that attempt.
Can they do anything if you don’t actually use them though lol
The slander bit.
I’ll use this for various things on my domain while having no actual involvement with cloudflare
