Yeah, my third party messenger tool (beeper) threw that same error. I'm guessing something went wrong in a deploy. Hopefully they'll roll it back soon.
I can still view pages when logged out, but trying to log in on an incognito window also fails (I didn't look at the console tho)
it's so funny how everytime services are down, their status page is like everything is normal here. I understand that there are internal politics around such things but still...
I find it very funny that the site scrapes Twitter to detect user complaints of downtime, so when Twitter is down there's going to be less downtime reports than usual
12 comments
[ 5.0 ms ] story [ 38.2 ms ] thread* [0]: https://downdetector.co.uk/status/twitter/
* [1]: https://api.twitterstat.us/
> {code: 353, message: "This request requires a matching csrf cookie and header."}
I can still view pages when logged out, but trying to log in on an incognito window also fails (I didn't look at the console tho)