Routing FAIL
jksluv
Newbie

i have a problem accessing "certain" websites.

and it seems like its either blocked by verizon(highly doubt) or theres problem with routing.

the website address is dreamdota.com which has ip address of 106.187.37.80

first i did some traceroute

as you can see, routing times out after 14th.

i tried all other solutions such as using open dns, changing the ip address and stuffs but no luck.

also tried to call/chat with verizon agents but they have no idea about routings.

keep asking me to reset the router/asking for remote control of my computer/firewall blah blah blah im done with these non-sense.

i thought it would be better to post it on the forum see if theres any actual expert knows the solution or maybe tech engineerer might see this and fix the routing issue.

thanks

EDIT: i did some of research and found out that this was not the first time they have problems like this.

they said i have to report the problem but i dont konw where to report them since call/chat agents dont even know what routing is.

0 Likes
Re: Routing FAIL
smith6612
Community Leader
Community Leader

I can't say for sure where the problem is, short of getting a traceroute from the server itself. In this case it seems to be getting off of Verizon's network so that rules out an issue with another site that is still broken (landzdown.com) but once it offloads from one network to another (it seems to be Sprint from the Japanese network and back ONTO the Japanese network, **bleep**? I might have to WHOIS those hops) it seems to have problems. Definitely smells like routing table issues again. I checked the Website on my end, and it is loading up. I'm at a location right now that is behind a Corporate Firewall, which hates anything Echo ICMP/UDP/TCP so I cannot provide a traceroute outbound for you.

Here's a Traceroute from a Verizon Business connection I manage which I obtained remotely. It has the same problems:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\>tracert 106.187.37.80

Tracing route to li380-80.members.linode.com [106.187.37.80]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.254.254
  2    30 ms    29 ms    31 ms  10.41.21.1
  3    30 ms    30 ms    29 ms  P2-1.BFLONY-LCR-01.verizon-gni.net [130.81.46.4]
  4    44 ms    43 ms    43 ms  P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
  5    43 ms    43 ms    44 ms  so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
  6    42 ms    43 ms    41 ms  so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.86]
  7    42 ms    42 ms    42 ms  0.xe-3-0-0.BR3.NYC4.ALTER.NET [152.63.2.241]
  8    45 ms    45 ms    64 ms  204.255.168.118
  9   126 ms   174 ms   126 ms  lap-brdr-03.inet.qwest.net [67.14.22.78]
 10   126 ms   126 ms   127 ms  63.146.26.70
 11   127 ms   127 ms   126 ms  lajbb002.kddnet.ad.jp [59.128.2.73]
 12   239 ms   242 ms   239 ms  otejbb204.kddnet.ad.jp [203.181.100.45]
 13   116 ms   116 ms   116 ms  sl-crs1-oro-0-3-0-0.sprintlink.net [144.232.25.131]
 14   117 ms   115 ms   125 ms  sl-crs1-stk-0-12-0-1.sprintlink.net [144.232.25.171]
 15   124 ms   123 ms   123 ms  sl-crs1-sj-0-12-0-1.sprintlink.net [144.232.9.224]
 16   122 ms   120 ms   120 ms  144.232.20.47
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   567 ms   552 ms   521 ms  otejbb203.kddnet.ad.jp [203.181.100.209]
 20   539 ms   574 ms   559 ms  cm-fcu203.kddnet.ad.jp [124.215.194.180]
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *     ^C
C:\Documents and Settings\>

0 Likes
Re: Routing FAIL
platgold36
Enthusiast - Level 2

this is a trace from network-tools.com

that entire trace is not in verizons network, so the routing issues are not related to verizon.

TraceRoute to 106.187.37.80 [li380-80.members.linode.com]

Host name
Hop(ms)(ms)(ms)      IP Address
1    0   0   0      206.123.64.46  -  
2    0   0   37      8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net  
3    0   0   0      4.69.145.126 vlan70.csw2.dallas1.level3.net  
4    0   2   0      4.69.151.146 ae-73-73.ebr3.dallas1.level3.net  
5    32   32   32      4.69.132.77 ae-3-3.ebr2.losangeles1.level3.net  
6    32   32   40      4.69.137.22 ae-72-72.csw2.losangeles1.level3.net  
7    32   67   32      4.69.144.79 ae-2-70.edge2.losangeles9.level3.net  
8    34   34   34      4.53.228.14 kddi-americ.edge2.losangeles9.level3.net  
9    34   34   34      59.128.2.105 lajbb002.kddnet.ad.jp  
10    147   147   147      203.181.100.45 otejbb204.kddnet.ad.jp  
11    160   160   161      124.215.194.180 cm-fcu203.kddnet.ad.jp  
12    148   148   148      124.215.199.122  -  
13    Destination host unreachable   Destination host unreachable   Destination host unreachable        -  
14    Destination host unreachable   Destination host unreachable   Destination host unreachable        -  
15    Timed out   Destination host unreachable   Timed out        -  
16    Destination host unreachable   Timed out   Destination host unreachable        -  

Trace aborted.

0 Likes
Re: Routing FAIL
scubasteve171
Enthusiast - Level 2
Just got new router. Nov 8. 1100am est. Plugged it in. It self configured. Now everything working fine here in s jersey. Wow! Ps. Verizon sent the router. Same stock model as before.
0 Likes
Re: Routing FAIL
jksluv
Newbie

yeah im getting a new router also. i hope this will fix the issue

0 Likes