Yep, seems like it!<p>The occassional existential reminder that it's Very Bad to be so dependent on a single platform....when Twitter goes down, my first instinct is to frantically search Twitter for information on the outage, putting me briefly into an unfun recursive loop.
Nitter and all its mirrors are still online. Nitter is better than the twitter site for many reasons, but I never imagined uptime would be one of them!<p><a href="https://nitter.snopyta.org/twitter" rel="nofollow">https://nitter.snopyta.org/twitter</a>
TweetDeck is also down, returning `{"errors":[{"code":131,"message":"Internal error."}]}`.<p>Edit: Looks like API calls from the Twitter web app are getting the same response too.<p>Edit 2: TweetDeck now loads a login page rather than the JSON error. API calls seem to be returning `{"errors":[{"message":"Over capacity","code":130}]}` now.
Quick HN question... I posted this as well (prior to this post) and it was "flagged"? I titled mine "Twitter is down hard". Perhaps my titling made it seem like I was trying to be mean or something? As a developer, I was trying to convey that it was very much down across all apps, sites, services. I thought that was the proper parlance but perhaps not.<p>To any HN admins, sorry! I meant nothing by it!
It’s been acting weird for days. A significant percentage of accounts I simply couldn’t ever reply to. Always the same accounts. But I could always reply to others.
Yeah, there's a spike on downdetector's chart: <a href="https://downdetector.com/status/twitter/" rel="nofollow">https://downdetector.com/status/twitter/</a>
<a href="https://downforeveryoneorjustme.com/twitter" rel="nofollow">https://downforeveryoneorjustme.com/twitter</a> still says it's up, definitely down though. Which is weird, normally they're pretty on top of things.
I was expecting/hoping to see the fail whale [1] again.<p>[1] <a href="https://www.techopedia.com/definition/1987/fail-whale" rel="nofollow">https://www.techopedia.com/definition/1987/fail-whale</a>
I get an API Error telling me "Failed to fetch user details for logout: Missing auth headers", and every other API call has an 403. If I go to "api.twitter.com" the domain does not exist.
Did anyone get a chance to screenshot Dave Troy's tweets from this morning? They were quite sharp, directed at Elon and Twitter Inc. Just a coincidence the platform goes down minutes after these tweets get posted?<p>Edit - had a tab open and managed to grab some of the points here: <a href="https://imgur.com/a/7AlBlXw" rel="nofollow">https://imgur.com/a/7AlBlXw</a>