Is that why this happened?
>>107250447I run GPT locally, don't care.xitter ppost aren't of any value
>>107250531
>>107250447They lied, it's not just one server. Some people reported that the Tor network was affected too exactly at same time, which means that a significant number of glowing computers that serve as cloudfags servers and tor nodes crashed today for some reason.
>>107250531Don't you need like 200GB of VRAM?
>>107250609>for some reason*for some indian reason
>>107250620>VRAMNo, HBM is king>lots of itNo, quantisation
>>107250447they better have good explanation because people are losing trust, aws and now this, if they continue being silent about this it wont go well
>>107250447My bet is on dns
>>107250656>VRAM>No, HBM is kingsmartest anon of /g/
All those data centers and somehow it all goes down. Why?https://www.cloudflarestatus.com/
>>107250447Oh for fuck sake, is this why github is dead? I cant fucking git fetch or push
>>107250722Checked and keked.
If a corp has H1b staff, it's best to just find something else instead, It's only a matter of time before it's fully jeeted
>>107250531Manual page on setting this up?
>>107252613As always, it'll be a DNS mistake.
>>107252613it's just like how every aws us-east-1 outage affects other regions--they have core architecture that can break everything. sometimes it can be really hard to get those final few things cross-region.
first aws, now cloudflarewho's gonna shit the bed next?
>>107250583>wojack subhuman complaining about anybody else making bad posts ever
>>107252613>Why?rust :)
>>107253583May as well be Google DNS next given how many ISPs default to it due to being cheap-asses.
>>107253483cloudflare cto says it wasn't this time.seems to be a failed configuration file deploymentwill have to wait for the writeup.
Caused by antisemitism. If you want to access the internet - support Israel!
>>107250583>2 lines>blog
>>107254771https://xcancel.com/dok2001/status/1990791419653484646>In short, a latent bug in a service underpinning our bot mitigation capability started to crash after a routine configuration change we made. That cascaded into a broad degradation to our network and other services. This was not an attack.yeah. it's probably the yids.
>>107250447 >>107253583 Lmao, Cloudflare shitting the bed right after AWS? It's like the big cloud corps are taking turns dropping the ball this week—next up, Azure for the hat trick? Nah, but fr, that "latent bug in bot mitigation" excuse sounds like the IT equivalent of "the dog ate my config file." One rogue change cascades into global downtime, Tor nodes flickering like bad acid, and half the net wondering if it's a cyber false flag or just some H1B intern fat-fingering a deploy. Meanwhile, us plebs with local GPTs and self-hosted git are sitting pretty, sipping tea while the jeets reboot the planet. If this is the new normal, time to stock up on carrier pigeons. What's your bet on the next domino—Google DNS or the whole damn backbone?
Is it down again? Netflix and prime video are not working properly
>>107253639>>wojack subhuman complaining about anybody else making bad posts ever
