Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Advertise on LowEndTalk.com

In this Discussion

Wired Slow ping
New on LowEndTalk? Please Register and read our Community Rules.

Wired Slow ping

dnwkdnwk Member
edited January 2013 in Reviews

I got some traceroute from my home (Verizon FIOS) to lease web and Digital Ocean. Not sure why, but they both have strange slow ping and package loss. Who's problem?

Traceroute to LeaseWeb

1 3 ms 4 ms 3 ms 192.168.2.1
2 16 ms 10 ms 10 ms L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
3 14 ms 12 ms 13 ms G0-9-3-1.WASHDC-LCR-22.verizon-gni.net [130.81.110.128]
4 59 ms 92 ms 77 ms ae0-0.RES-BB-RTR1.verizon-gni.net [130.81.209.114]
5 12 ms 16 ms 13 ms 0.so-2-0-3.XL4.IAD8.ALTER.NET [152.63.30.13]
6 18 ms 21 ms 22 ms TenGigE0-7-1-0.GW1.IAD8.ALTER.NET [152.63.35.149]
7 * 115 ms 125 ms teliasonera-test-gw.customer.alter.net [63.65.76.190]
8 16 ms 15 ms 15 ms leaseweb-ic-150718-ash-bb1.c.telia.net [80.239.196.198]
9 17 ms 15 ms 15 ms 108.59.15.117
10 115 ms * 118 ms 108.59.15.22
11 159 ms 202 ms 205 ms 198.7.57.56

Traceroute to Digital Ocean [NY]

1 4 ms 3 ms 3 ms [192.168.2.1]
2 12 ms 9 ms 11 ms L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
3 14 ms 15 ms 15 ms G0-9-3-1.WASHDC-LCR-21.verizon-gni.net [130.81.109.154]
4 14 ms 12 ms 13 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.30]
5 110 ms 110 ms 183 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
6 12 ms 15 ms 13 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137]
7 124 ms 120 ms 110 ms vl-3603-ve-227.ebr2.Washington12.Level3.net [4.69.158.42]
8 111 ms 110 ms * ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
9 116 ms 115 ms 123 ms ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102]
10 108 ms 107 ms 108 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 119 ms 115 ms 152 ms SERVERSTACK.edge3.Newark1.Level3.net [4.28.6.70]
12 43 ms 34 ms 30 ms [192.34.61.245]

To another Digital Ocean site in NY

1 <1 ms <1 ms <1 ms 192.168.2.1
2 8 ms 7 ms 8 ms L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
3 10 ms 13 ms 10 ms G0-9-3-1.WASHDC-LCR-21.verizon-gni.net [130.81.109.154]
4 10 ms 10 ms 10 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.30]
5 109 ms 110 ms 110 ms 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141]
6 * 107 ms 140 ms ae16.edge1.washingtondc12.level3.net [4.68.62.133]
7 * 104 ms 116 ms vl-3603-ve-227.ebr2.Washington12.Level3.net [4.69.158.42]
8 107 ms 101 ms 105 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
9 112 ms 121 ms 122 ms ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102]
10 108 ms 104 ms 105 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 132 ms 118 ms 115 ms SERVERSTACK.edge3.Newark1.Level3.net [4.28.6.70]
12 113 ms 113 ms 115 ms 192.81.208.83


It looks like there are problems somewhere in DC's local exchange.
Am I right?

Designers: www.linkun.info

Comments

  • You'll only know for certain if you can run a trace back to your wan address.

    It's clear that

    4 14 ms 12 ms 13 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.30]
    5 110 ms 110 ms 183 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]

    Is an issue though- probably saturated- the question would be what it looks like back to you. (level3->verizon or something within verizon before l3)

    Either way good luck getting them to look into it. If you're willing to spend time on with tech support rebooting your modem, pc, etc. to get a ticket created :D

    Retired!

Sign In or Register to comment.