Staff reply here, sorry it took a couple of days.
I have measured this from our side, so here is what we can actually see rather than guess.
The tracker is up and has been throughout. It answers from here in a few hundredths of a second, the site is fine, and nothing was taken down or put into maintenance.
The more useful part: several people posting in this thread are announcing to our tracker right now, this minute, while I am writing this. So there is no outage. And for the accounts reporting the problem, our tracker has never seen a single announce arrive. Not a rejected one, not a failed one. Nothing reaches us at all.
That combination has only one shape. Your client's announce is being stopped somewhere on the path before it gets to us. It is also why the site still loads in your browser while your client cannot reach the tracker, and why a VPN or mobile data fixes it the second you switch, exactly as some of you found. Web traffic and the announce take different routes, and only one of them is being interrupted.
What we cannot see from here is whether that is deliberate filtering or something broken at your provider, and I would rather not put words in anyone's mouth. One of you mentioned other services failing at the same time, which reads more like a fault than like targeting. Either way it is not something we can fix from this end, and there is nothing wrong with your accounts.
What actually helps: a VPN, and it has to cover the torrent client, not only the browser. Mobile data works too. If it turns out to be a fault rather than a filter, it should clear by itself.
Thanks to the people who did the legwork in here, especially testing a second client and mobile data. That is what let us tell the difference from our side.
