3 ms·
I am following up internally. Looks like there's a combination of this data not being cached, our systems thinking a DDoS was happening (which it sort of was).
by jgrahamc 4y ago
I am following up internally. Looks like there's a combination of this data not being cached, our systems thinking a DDoS was happening (which it sort of was). But getting the full story now.
- deleted 4y ago[deleted]
- Yeri 4y agoSeems like MP says it’s fixed: https://twitter.com/tuinslak/status/1583016022491435009?s=61&t=N9WX0bnYDZTkDrEbKWfxMw https://twitter.com/tuinslak/status/1583016022491435009?s=61...
- solardev 4y agoI'm glad they sorted it out, but I wish there was a proper support route other than "create a sufficient media storm so that an employee tweets the CEO"