4 ms·

Worth noting Twitter’s status page claims it is “operational” and no events are listed under history section for past 180-days, which is obviously wrong: - htt

Worth noting Twitter’s status page claims it is “operational” and no events are listed under history section for past 180-days, which is obviously wrong: - https://status.twitter.com/ https://status.twitter.com/ * Not to mention the SSL certificate appears to be expired too. ———- EDIT-01: Appears there’s a status page just for the API: - https://api.twitterstat.us/ https://api.twitterstat.us/ EDIT-02: Wow, Twitter is using Twitter to post status updates: - https://twitter.com/TwitterSupport/status/1632792942262747136 https://twitter.com/TwitterSupport/status/163279294226274713...

juujian 4y ago
> * Not to mention the SSL certificate appears to be expired too. Love that detail. Just the icing on the top that says "everybody who was vaguely aware of this particular infrastructure is gone."
- O__________O 4y ago
  Also weird given that Twitter is using 3rd-party service which apparently doesn’t even automatically log and post known downtime issues; service being: https://status.io/ https://status.io/ (Assuming this is more of a the site’s not down unless the CTO says it is services.)
- tcmart14 4y ago
  Oh man, no way. If that is the case, some people thought I was full of shit when I said, "watch it, in the mass layoffs they fired that one guy who knows all about the certs." There is always that one guy and unfortunately he always gets canned.
banana_giraffe 4y ago
It's not expired. That site is using the wrong cert (ERR_CERT_COMMON_NAME_INVALID). How odd.
- Joker_vD 4y ago
  Browsers still look at the commonName?.. Hasn't this field been deprecated since 2000?
  - k_roy 4y ago
    CN/SAN. It amounts to the same thing. They are serving the cert for "*.twimg.com" here.
johnbellone 4y ago
They're not expired. It looks like they're serving up the wrong one for that domain.
deleted 4y ago
[deleted]

juujian 4y ago

> * Not to mention the SSL certificate appears to be expired too. Love that detail. Just the icing on the top that says "everybody who was vaguely aware of this particular infrastructure is gone."

O__________O 4y ago
Also weird given that Twitter is using 3rd-party service which apparently doesn’t even automatically log and post known downtime issues; service being: https://status.io/ https://status.io/ (Assuming this is more of a the site’s not down unless the CTO says it is services.)
tcmart14 4y ago
Oh man, no way. If that is the case, some people thought I was full of shit when I said, "watch it, in the mass layoffs they fired that one guy who knows all about the certs." There is always that one guy and unfortunately he always gets canned.

banana_giraffe 4y ago

It's not expired. That site is using the wrong cert (ERR_CERT_COMMON_NAME_INVALID). How odd.

Joker_vD 4y ago
Browsers still look at the commonName?.. Hasn't this field been deprecated since 2000?
- k_roy 4y ago
  CN/SAN. It amounts to the same thing. They are serving the cert for "*.twimg.com" here.

johnbellone 4y ago

They're not expired. It looks like they're serving up the wrong one for that domain.

deleted 4y ago

[deleted]