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?
Do you understand I never called it one.
You did while building Yet Another Strawman Of Something Nobody Said But You Want To Argue About.
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?
No.
Because you again didn't bother to actually read what qualifies as a report they actually record as valid despite it being suggested you check multiple times.
A small number of users reporting a problem does not constitute a large-scale incident. To make sure that incidents are correctly represented, Downdetector calculates a baseline volume of typical problem reports for each service monitored, based on the average number of reports for that given time of day, measured over the previous year. Downdetector only reports an incident when the number of problem reports is significantly higher than the baseline.
Downdetector only accepts the first report for a specific company from a single user. Subsequent information about the issue is collected, but is not counted as a new problem report.
So no, you can't just go have a bunch of Elon haters spamming a bunch of complaints to cause a massive spike in problems.
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.
You appear to be confusing "comments" with "reported outages"
Are you SURE you do anything, at all, with IT? Because it never sounds like it.
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
*rotlf*
According to that page there's been no downtime... of anything... for months.
ZERO people have had problems with the service. For months.
I agree one of us is using ridiculously bad data, but it ain't me
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)
Another ROTFL situation.
Know what those guys ACTUALLY do?
YOUR source said:
We monitor the official status pages of more than 2,560 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more
So they just record whatever the same previous ridiculous source tells them.
According to it twitter has had zero problems for almost 2 years (as far as their data seems to go back)
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)
Right, which is again why it's so laughable you're citing it. Doubly so since they appear to do the same thing the previous link does- just monitor the official twitter status page which keeps showing 0 downtime.
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)
I mean, they have a ton less users, so obviously total reports is lower...but then so is their baseline # they're comparing it to.
But did you notice that the report rate they DO have is
much higher than normal? As much as double normal at several points on the graph.
So no, it's NOT at "historical norms" as you claimed. As specific examples on the current chart- it shows DOUBLE the historic norm error rate at 23:40 right at the start of the 24 hour period... Near DOUBLE again around 7:40, and at least 50% above norm a bunch of other times in that 24 hours.
So just like downdetector they're showing more problems recently.
Thanks for confirming it was right
Care to retract your statements now?
Why? It remains, unlike your stuff, 100% accurate.
YOUR sources keep saying 0 problems, not for months (or YEARS).
But we KNOW FOR A FACT there's been more than 0. Just a few days ago Elon broke 2FA for a while because he didn't understand what service did what for example and turned off the one that actually sends the 2FA codes.
This was widely reported.
But somehow NOT recorded as any sort of problem on twitters own status page you cited... and thus not recorded as a problem on the other nonsense links you gave that do nothing but repeat what the official pages says.
I'd ask if you wanna retract yours in the face of a specific example debunking your claims, but I know better than to ever expect you to recognize your mistakes