with no problem while using T-mobile LTE network.
Hello!
It seems there is a routing problem to that website, it can be accessed from other networks, but Verizon's core routers don't seem to be routing to it. Have you contacted support? This is an issue with Verizon's network, unfortauntely us fellow users can't be of much more asssistance in this case.
Looks like a routing issue caused by the network failing to ingest information via BGP. The route looks to be propagating to AS701 (Verizon Business) via an announcement from China Unicom but breaks down beyond that. No issues reaching China Unicom itself here.
There's also a BGP Announcement coming via China Unicom NGCN which can then be advertised to Verizon via Level3. This could also be complicating the situation if there's information being propagated across which violates Verizon's network configuration, but is very unlikely as this is an otherwise common situation.
Your connection should route like this: Verizon Online > Verizon Business (UUNet / MCI / VZB - Tier 1 Backbone) > China Unicom Americas > China Unicom Beijing > Beijing HuaxiaYakue Network Technology Co., Ltd (The hosting group). The trace will hand off from Verizon Business to China Unicom in San Jose, CA. Verizon prefers to use China Unicom directly versus using the Level3 handoff unless VZ loses their peer with China Unicom as this is the least costly route from a networks perspective.
For what it's worth, the entire 182.18.32.0/19 subnet looks to be currently unreachable via Verizon. I can't route to any IP I've tried in the subnet (No I'm not going to check all 16,000 IPs).
Tracing route to 182.18.60.148 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 179 ms 274 ms 257 ms 10.41.7.1 3 P0-0-1-0.BFLONY-LCR-21.verizon-gni.net [130.81.35.184] reports: Destination net unreachable. Trace complete.
Here's a trace to Kongzhong's main server on a different IP but in the same subnet as the random IP I chose above:
Tracing route to 182.18.61.37 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 356 ms 366 ms 383 ms 10.41.7.1 3 P0-0-1-0.BFLONY-LCR-22.verizon-gni.net [130.81.33.46] reports: Destination net unreachable. Trace complete.
The BBS host:
Tracing route to bbs.bg.kongzhong.com [182.18.61.38] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 191 ms 128 ms 107 ms 10.41.7.1 3 P0-0-1-0.BFLONY-LCR-22.verizon-gni.net [130.81.33.46] reports: Destination net unreachable. Trace complete.
An IP address with multiple websites on it at the far end of the subnet:
Tracing route to 182.18.63.100 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 105 ms 157 ms 115 ms 10.41.7.1 3 * * P0-0-0-0.BFLONY-LCR-22.verizon-gni.net [130.81.136.32] reports: Destination net unreachable. Trace complete.
So the TL;DR to this is: A network engineer needs to fix this. Not exclusive to the BBS you're trying to reach, but with ther entire IP address subnet the BBS resides in.
From a consumer standpoint, please reach out to the Verizon Direct team at DSLReports, and report this information. They are Verizon's Social Media team, which has pretty good contacts with Verizon's network team to work this out.
https://www.dslreports.com/forum/vzdirect
If Verizon says the problem is not with them, it's more than likely the hosting company in Beijing needs to ensure they're not feeding bad information to China Unicom, and that China Unicom isn't feeding bad information to Level3 and Verizon.
If you were the website owner, I'd direct you to talk to the hosting company. As my Chinese is a bit rusty, searching on Chinese search engines for this company isn't exactly feasible, and the WHOIS records are not super helpful beyond the name. 🙂
Start a new topic or ask questions in the open forum.
