New ISP IP Address Blocked

[Alchemist666]

Hi there,

My public IP, 102.23.127.183, is currently being blocked by your system, I think. Rendering me unable to open your site, forums and launcher.

I currently work for my ISP and saw that not a single friend of mine using the same ISP (IP Range) can access your site, forums or launcher either.

I have attached an image from Network Platforms and Cogent advising us that it’s not them that’s blocking the IP and that our entire range is being blocked. I tried emailing in at first but was told to come to the forums. Since I can’t access it, I had to purchase a month of some other VPN just to access it.

If need be I also have screenshots of trace routes that I ran from our IP range to your servers.

Hoping you can assist

[weongyo]

@Alchemist666 Is it still same? We have a IP blocking logic for 24 hours if you tried to input wrong ID/PWD multiple times (at least 10 times).

However I’m not sure that it’s your case.

[Alchemist666]

Hi @weongyo

Yeah it’s still the same on my end. I don’t think it’s what you explained as our entire IP range can’t even reach any point where login is required. And on my side, I have my details cached so it’s auto-fill.

[weongyo]

Frankly we didn’t do anything to block your IP. It means this IP blocking issue could be happening at the upstream ISP.

[Alchemist666]

Hi @weongyo

Thanks for the reply. I have sent it back to the upstream provider and they replied with the following:

“Please send them the traceroute from a working IP and a non-working IP to show that the IP dropping the traffic is on their network. 38.104.85.146
As you have seen from the traces, we are passing the traffic to PCCW who in turn pass it on to Cogent and the failure occurs when Cogent pass the traffic on to them. Please ask them for a reverse traceroute to your IP as well.”

I have attached both screenshots. A trace from a working IP and a trace from our range.

[Alchemist666]

The IP you can use for the reverse trace is 102.23.125.129

[weongyo]

Okay. When I checked the traceroute from mudfish website, it shows the following result:

$ traceroute 102.23.125.129
traceroute to 102.23.125.129 (102.23.125.129), 30 hops max, 60 byte packets
 1  r-291062-VM.csdd2cloud.internal (172.2.0.14)  0.242 ms  0.220 ms  0.193 ms
 2  14.63.22.2 (14.63.21.2)  0.463 ms  0.480 ms  0.465 ms
 3  14.63.28.177 (14.63.28.177)  0.437 ms  0.425 ms  0.409 ms
 4  14.63.208.65 (14.63.208.65)  1.152 ms 14.63.208.133 (14.63.208.133)  1.218 ms  1.207 ms
 5  * * *
 6  * * *
 7  112.174.26.146 (112.174.26.146)  2.169 ms 112.174.66.62 (112.174.66.62)  3.743 ms 112.174.66.106 (112.174.66.106)  48.845 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

So if I understand this issue correctly, it seems the upsteam ISP of mudfish blocks your IP. Let me check with our provider for mudfish.

[Alchemist666]

Hi @weongyo

Thanks for the test. Yeah that’s what I understand as well. Our upstream provider said if you guys are not blocking our IP ranges then it’s your upstream provider mentioned at the start. I believe it’s either Cogent or Korea Telecoms