Firecow

Devops Engineer at Cego A/S and open source author

[Firecow @MadsJonNielsen]

@discord @Cloudflare implemented a fix for something, about the time @discord went bongers. Perhaps its related.

[Firecow @MadsJonNielsen]

@discord Think you got some problems.

[Firecow @MadsJonNielsen]

https://t.co/5HcIvSngwk

New release out of gitlab-ci-local 🥳

[Firecow @MadsJonNielsen]

Something isn't right.
I'm timing out to https://t.co/EW6etQ3Ewm from three different type of network connections.
@githubstatus @github

[Firecow @MadsJonNielsen]

@Cloudflare Discord and the company I work for are experiencing images not being served correctly, causing the Discord client to not start properly.
I disabled HTTP3 in our dashboard and it solved the issue immediately...
You should properly have a look at what was deploy 12:00

[Firecow @MadsJonNielsen]

@MaddoxJack @discord @gen_stamps This is not a client problem.
A technician needs to disable Cloudflare's HTTP3 feature.
They pushed a bug to their edges around 13:00 UTC.

[Firecow @MadsJonNielsen]

@ikilledhundreds @discord This is not a client problem.
You need to get a technician to disable Cloudflares HTTP3 feature.

[Firecow @MadsJonNielsen]

@MaddoxJack @discord It's not a client problem, you need to get a technician to disable Cloudflare's HTTP3 feature.
They must have pushed a bug to their edge nodes.

[Firecow @MadsJonNielsen]

@bonuspoppa @discord @discord Cloudflare have pushed a QUIC bug into their edges.
Have a technician disable Cloudflare's HTTP3 feature, asap.

[Firecow @MadsJonNielsen]

@discord You need to disable cloudflare http3.
@Cloudflare must have pushed some mistake to their edges...