- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
true. that's why i said on my previous post in this case i'll just have to live with VPN.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jackc, did your issue actually get resolved? i believe i am having the same problem, one symptom on my end is extremely high packet loss when conducting skype call. we did a few controlled tests, such as connecting to the same party in China from another connection (such as timer warner's from my neighbor), switched out a few routers, etc. it all points to the problem you suggested. would appreciate it if you could share any tips. thanks so much!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
he marked it as solved because there is nothing that people here on the board could do to help.
It was a routing issue outside Verizon. There is slim hope that Verizon would re-route the routing to avoid sprintlink. No chance of getting sprintlink to increase bandwidth.
The only thing to try for this issue was to go to dslreports and post there and hope that Verizon would re-route.
How do your tracerts look?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thanks for the note. my traceroute from last night looks like this. i am no expert, do you see any obvious problems from this report?
VERIZON FIOS 2010.6.1-10:52pm
traceroute to 218.83.155.2 (218.83.155.2), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 1.010 ms 0.483 ms 0.419 ms
2 74.108.111.1 (74.108.111.1) 2.206 ms 2.172 ms 2.047 ms
3 g3-0-6-1308.nycmny-lcr-13.verizon-gni.net (130.81.177.80) 4.944 ms 4.464 ms 4.418 ms
4 so-6-3-0-0.bb-rtr1.sea01.verizon-gni.net (130.81.28.52) 5.288 ms 5.287 ms 5.323 ms
5 0.so-0-0-0.xl3.nyc4.alter.net (152.63.1.41) 6.340 ms 6.168 ms 6.355 ms
6 0.xe-5-0-0.br3.nyc4.alter.net (152.63.16.181) 5.409 ms
0.xe-8-1-0.br3.nyc4.alter.net (152.63.17.53) 6.427 ms
0.xe-5-0-0.br3.nyc4.alter.net (152.63.16.181) 5.242 ms
7 sl-crs2-nyc-0-1-2-0.sprintlink.net (144.232.18.237) 7.627 ms 7.773 ms
204.255.168.118 (204.255.168.118) 8.418 ms
8 sl-crs2-chi-0-5-0-0.sprintlink.net (144.232.20.162) 43.092 ms
sl-crs2-pen-0-8-3-0.sprintlink.net (144.232.20.97) 15.427 ms
144.232.18.208 (144.232.18.208) 18.380 ms
9 sl-crs1-stk-0-4-0-2.sprintlink.net (144.232.8.169) 104.106 ms 113.831 ms 114.943 ms
10 sl-crs2-sj-0-14-0-0.sprintlink.net (144.232.24.34) 94.873 ms
sl-crs1-sj-0-2-2-0.sprintlink.net (144.232.20.113) 138.021 ms 117.587 ms
11 sl-st20-sj-0-0-0.sprintlink.net (144.232.18.106) 97.947 ms 93.715 ms 91.491 ms
12 sl-china1-7-0.sprintlink.net (144.223.242.126) 313.928 ms 317.458 ms 311.827 ms
13 202.97.50.77 (202.97.50.77) 344.874 ms 348.579 ms 340.814 ms
14 202.97.50.109 (202.97.50.109) 455.845 ms 458.797 ms *
15 202.97.33.253 (202.97.33.253) 464.717 ms 458.871 ms 463.128 ms
16 202.97.33.89 (202.97.33.89) 448.587 ms 449.789 ms 457.534 ms
17 * 61.152.86.173 (61.152.86.173) 464.598 ms 467.808 ms
18 61.152.81.22 (61.152.81.22) 453.682 ms 445.625 ms 509.638 ms
19 124.74.254.42 (124.74.254.42) 454.527 ms 458.911 ms 452.928 ms
20 124.74.254.41 (124.74.254.41) 443.591 ms * 438.447 ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
from the looks of it, you're having issues with sprintlink too. Now of course there may be more going on than actually shows on a tracert but at first blush it looks like the problem starts at about hop 9, although hops 9, 10, and 11 are a little slow they dont look too bad. But Hop 12...Thats where it really starts. The problem is that first its sprintlink, thats always bad news. But in addition, its sprintlink in China. Now having said that and seeing a relatively slow connection starting at hop 12, it does look fairly stable. No wild fluctuations, no spikes, just slow responses for what we are used to here. That could be due to the distance involved. It is also likely that the Chinese infrastructure is not as robust as ours (LOL). The fact that it happens more at night (other poster) is likely due to that it may be night for us, but its daytime for them, so their network gets hammered at that time. You could try going over to dsl reports (see previous post for link) and see if Verizon can re-route. But likely there is nothing that can be done as for the most part the network looks good until you get the china.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm seeing the same problem from PA. I have been using VPN as work arounds right now since Verizon is incapable of coming up with a solution after numerous calls with their tech support. This is definitely outrageous and frustrating.
- « Previous
-
- 1
- 2
- Next »