@frankdavao48 said:

I'm blocked again, using google dns. When testing https://tracker.gaytor.rent/stmdd/ results to "the connection has timed out." I actually have trouble accessing some sites at work last week, same time I encountered the issue on the trackers. I've seen some posts online as well, that some people are blocked and cant access specific work related sites/apps. Can't be a coincidence, this ISP is sht. As somebody who is working from home, I can't rely on this ISP. I am switching.

Yes... It sounds like they may be trying to force DNS requests to redirect to their servers specifically, which aren't always answering requests reliably.

The tracker is up and has been throughout — right now it is serving over two million seeders, and announces from the rest of the world are arriving normally. Nothing changed on our side.

What we see from the support desk matches this thread exactly: since roughly the start of the month, members in the Philippines report the tracker as offline or timed out while the website itself loads fine, and every one of them who has tested it finds that a VPN or mobile data brings the tracker straight back. That combination — site reachable, tracker not, VPN fixes it — means the block is between you and us, at the provider, not in your client and not on our end.

frostycab's test is the right one. Open https://tracker.gaytor.rent/stmdd/ in a browser. If it loads, your provider is not blocking the tracker hostname and something else is going on. If it will not load, or only loads through a VPN, that is the answer.

Two things that help:

A VPN works, but it has to be running while your torrent client is running, not only in the browser — the client makes its own connections.

Changing your DNS to 1.1.1.1 or 9.9.9.9 sometimes gets past this, if the block is at the DNS level. If they filter deeper than that, it will not, and the VPN is the way.

There is nothing we can change from here that would undo a block your provider has put in place. If it lifts, you will simply see the tracker come back on its own.

Also I got tired of tweaking the settings related to DNS and stuff, it was a sleepless night for me. That was why i bought a VPN subscription.

You are awesome.

The DNS is responsible for mapping the server's domain & IP, but the DNS alone is not responsible for routing the traffic. That is, if using a different DNS makes the tracker reachable, the ISP is not blocking its IP.

That is still insufficient to say it is definitely a temporary fault or an intentional filtering. But if it's intentional, you can expect a custom DNS to also stop working eventually, if they start blocking IPs.

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.

i ask because, like i said in my previous response, if this is in fact a bad routing situation, it will affect all clients, that doesn't mean it is intentional. but it might as well be, the fastest way to know would be contacting the ISP directly, but depending on the country's laws it might not be a wise idea.