Sigh, so hard-headed. LMGTFY.
OK, let's clear the air on this properly.
1) Do you understand that downdetector is not a "monitoring" service? In the industry a "monitoring" service has a VERY strict and narrow definition - it it's actual SERVER TO SERVER automated communications with the purpose of establishing uptime records. Specifically, someone has setup one or more servers that reaches out to a server(s) to be monitoring (in this case Twitter) and obtains status on that server. In this case I would have a server setup to query twitter.com every 1, 5, 10, etc. seconds and verify that it is up. Anyone in this industry that isn't new will set this up from multiple geographically distinct monitoring servers, so that if there is a problem with a link between origin and destination (i.e. with an ISP fiber break, a down carrier router in the middle, etc.) we don't get a false positive.
downdetector IS NOT a monitoring service. By their own methodology here they are a "user reporting service":
That means what you are reporting is no more than a bunch of users that have gone to downdetector and reported something is offline or has a problem for them. Well, that seems a little bit ripe for abuse, perhaps, no?
Well, how might we sus this out, if it is possibly being abused? Oh, there's a comments section for downdetector on the twitter status page . . . . lets look at that and see what's in there. Oh my, lots and lots of Elon hate in there. Even some people admitting that they are falsely saying things are down just to make Elon look bad. Well, that doesn't seen like this is a very reliable dataset . . . it's user-reported, and the users are self-reporting they are submitting falsified data . . . hrm. Food for thought.
So, can we do better? Perhaps.
2) Twitter maintains and updates a status page. That page gives ALL kinds of insight into what is going on at the server and software/api/services level. That page can be found here, with more than 24h of historical data:
api.twitterstat.us
And if you want to go beyond 2 weeks of historical data, then you can look through the internet archive for that same page here:
web.archive.org
Now, it's not the most granular page, it doesn't give hour by hour stats, but it does give a ton of service-level data (i.e. what actually runs behind the scenes).
This kind of page is built by 3rd party software (we use it for Uber.com and some other of our clients). It's very accurate and reliable. The argument of "this can be faked so twitter doesn't look bad" doesn't hold a lot of weight with those of us that run hosting and software services.
But just in case Twitter might be faking their own data (and doing so long before Elon showed up, it would appear), let's find some reliable 3rd party monitoring sites that are NOT based upon subjective user reports.
3) Well, there are a decent number of automated status detectors (i.e. those that DO NOT rely upon user reports) that also monitor twitter:
Twitter Status. Check if Twitter is down or having problems. | StatusGator (no reported outages in the past 24 hours, AND they give historical data for Sept, Oct, and Nov 2022 - all report no outages)
Is Twitter Down? Check Twitter status and current outages (this one is also an automated monitor - also reports ZERO outages for the past 7 and 30 days)
https://istheservicedown.com/problems/twitter (this one is also partially user-reported, but ironically the huge number of downtime reports don't correspond to what is on downdetector - we are at historical norms on this one)
Twitter Down? Service Status, Map, Problems History - Outage.Report (another user-level reporting site, but doesn't show a large spike for downtime - see left checkerbox for past 60 days and hover over a day for the number of down reports).
So yeah, people are using downdetector to "report" that Twitter is down much more than normal for them, when in fact, all other non-biased and objective data seem to say it's running normally.
Care to retract your statements now?