Seems that their api for their web app is currently returning a 503 from POST https://api.twitter.com/1.1/onboarding/sso_init.json

Response payload: {"errors":[{"message":"Over capacity","code":130}]}

And then it redirects to https://twitter.com/logout/error

Musk unplugged one too many racks in their datacenter?

for the context https://twitter.com/elonmusk/status/1606624671100997634

Funnily enough, their API status page still reports all green:

https://api.twitterstat.us/

I suspect that the services responsible for detecting outages were among those that got nixed

So, traditionally, AWS's status page only grudgingly updates from green tick to green tick with information box after about half an hour of people complaining about AWS problems on Twitter.

Which raises the question; if Twitter is down, will any status pages ever be updated again?

Those status pages are useless these days. Basically everyone always says stuff is running fine, even when they have total outages.

     status pages are useless these days

Now there is a start-up idea to use Ai. Report on the misalignment of reality to document dashboard status. Picture a second or third opinion as a service.

I don't have a twitter account but something is very different now. Before twitter always brought up a dialog asking me to accept notfications but it doesn't anymore. It also would bring up a dialog when you scroll too far in a thread that I need to log in to see the rest of the conversation, that is also now missing. Twitter seems to have lost all user hostility for people not logged in.

Btw, you can click “login” and then will get a chance to close that pop up if you want to continue reading without an account. There’s simply no way to close it from the first view.

Twitter homepage doesn't work.

Viewing a user's page works. Viewing a specific tweet works. Twitter app works.

The homepage works fine for me, but I'm already logged in.

Crazy swing in the prediction market: https://manifold.markets/MP/will-twitter-suffer-a-major-outa...

Whoops. After many people praising Musk cutting tons of workforce and it still running... What percentage of Twitters engineers were cut / left, does anyone know?

This won't be blamed on the lack of employees, it'll be blamed on "the weather" or "poor coding practices from those we let go".

> Something went wrong, but don’t fret — it’s not your fault. Let’s try again.

That's what I get when I try to login.

Unsurprisingly, trying again doesn't help

First it failed on my desktop browser, and 5 minutes later it kicked me out of mobile. Currently unable to login.

I don't think it's Twitter, I think it's the weather/rolling blackouts and the Internet. YouTube has been giving me more problems just loading thumbnails for days, and I'm on fiber.

They so need to change their 4xx and 5xx error page to the "y'all been musked" cowboy kid

Makes sense the API is incurring issues. Nitter is also returning a 593 error.

Is Musk aware of Nitter and does/would he even care if so?

As of now, new tab doesn't keep session.

I cleared my cache and it works fine now.

Seems to be still up and running.

Seems up at the moment

Are you logged in?

I'm currently sort of logged in. I have tabs that are logged in but clicking links to tweets gives me tabs that aren't logged in.

I don't understand the downvotes. I am logged in to Twitter and some page loads are not recognizing that, just as I describe. This is "sort of logged in".

> sort of logged in

lol