Everything is back to normal now. Yes, it was an attack, not legitimate traffic. No, we don't know who was behind it. I agree the timing with Twitter being down was unfortunate.
Top-level
Eugen Rochko
Everything is back to normal now. Yes, it was an attack, not legitimate traffic. No, we don't know who was behind it. I agree the timing with Twitter being down was unfortunate. 37 comments
Eugen Rochko
Fastly and Datadog who both sponsor us by providing us a free service were instrumental in analyzing and mitigating the attack. Shout out to our own team as well, glad I don't have to do this alone anymore!
i am root
@Gargron I know the team is busy, but could you please prioritize requests for adds/changes to instances on https://joinmastodon.org/servers? Not waiting on anything myself, but have seen several other #MastoAdmin reporting a lack of any response. During these Twitter and mastodon.social outages, it would be very helpful to have more places for users to land.
Purple :verified:
Jeff the Alien
@Gargron Will there be a blog post detailing what and how it all happened, and list any IOCs, etc.?
Dan Gillmor
ππ¦πππ€ πΈπ₯ππππ€
@Gargron Are you not employing any sort of rate-limiting?
John Carlsen
I still see this via US-CA-SJ: Error 403 Forbidden Error 54113 Varnish cache server
DHeadshot's Alt
@Gargron I'm getting 403 errors trying to access the site - am I blocked then? I didn't do anything apart from try to load my timeline while you were down!
Dr. Jorge Caballero
@Gargron Third time in 2 weeks that the timing is "unfortunate" for a major Mastodon server or API endpoint π |
@Gargron maybe the api team at twitter got reassigned to ddos attack mastodon