| embarq dsl 3/512 vs my cable internet insightbb [Broadband] TRYING Embarq DSL
well Im tring embarq dsl at the moment 3.0/512
TRACERT to dsl reports
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 62 ms 62 ms 62 ms
2 83 ms 85 ms 83 ms crohmnfd02 [69.69.33.245]
3 94 ms 93 ms 93 ms sl-gw31-chi-4-1.sprintlink.net [160.81.42.5]
4 93 ms 93 ms 93 ms sl-bb21-chi-4-0.sprintlink.net [144.232.26.29]
5 101 ms 98 ms 96 ms sl-bb22-chi-15-0.sprintlink.net [144.232.26.97]
6 95 ms 94 ms 94 ms sl-st21-chi-11-0.sprintlink.net [144.232.20.21]
7 98 ms 97 ms 97 ms ggr3-p330.cgcil.ip.att.net [192.205.33.157]
8 117 ms 116 ms 116 ms tbr1033901.cgcil.ip.att.net [12.123.4.246]
9 121 ms 120 ms 120 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
10 116 ms 116 ms 116 ms 12.122.84.41
11 116 ms 118 ms 116 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
12 120 ms 119 ms 119 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
13 122 ms 121 ms 121 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
14 121 ms 123 ms 121 ms www.dslreports.com [209.123.109.175]
insight tracert to www.dslreports.com
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 8 ms 6 ms 7 ms 74-132-56-1.dhcp.insightbb.com [74.132.56.1]
2 24 ms 15 ms 22 ms 74-132-0-173.dhcp.insightbb.com [74.132.0.173]
3 9 ms 11 ms 11 ms 74-132-0-89.dhcp.insightbb.com [74.132.0.89]
4 10 ms 11 ms 14 ms 74.128.8.201
5 43 ms 33 ms 28 ms so-3-1-0.gar2.Atlanta1.Level3.net [4.78.214.21]
6 27 ms 27 ms 25 ms ae-1-51.bbr1.Atlanta1.Level3.net [4.68.103.1]
7 62 ms 42 ms 55 ms ae-2-0.bbr1.Washington1.Level3.net [4.68.128.201
]
8 128 ms 108 ms * ae-23-52.car3.Washington1.Level3.net [4.68.121.4
8]
9 68 ms 47 ms 71 ms att-level3-oc192.Washington1.Level3.net [4.68.12
7.154]
10 50 ms 50 ms 49 ms tbr2-p033401.wswdc.ip.att.net [12.123.8.118]
11 51 ms 48 ms 64 ms tbr2-cl15.n54ny.ip.att.net [12.122.10.53]
12 69 ms 49 ms 53 ms gar1-p370.nwrnj.ip.att.net [12.123.0.157]
13 51 ms 58 ms 51 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
14 57 ms 61 ms 57 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
15 51 ms 74 ms 49 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
16 52 ms 52 ms 52 ms www.dslreports.com [209.123.109.175]
Trace complete.
seems insight doing a little better on the tracert ping time
but 2 less hops with dsl 14 vs 16 |
|
|
|
| Call Tech support for Emarq, ask for level 2. Tell them you installed VOIP and are having some lag issues. Ask them to put you on fast path. You may have to get demanding to get this done. You will like the results. They will only do this for VOIP Problems. |
|
 MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | reply to indy0365
Sprint's strong point has never been latency. |
|
| said by Maxo:Sprint's strong point has never been latency. And that is sad. And possibly due to poor infrastructure. I mean you are talking about a network here. If properly setup there should be no excess latency than normal network expansion latency.
When a network is geographically separated you're going to have latency, but this is ridiculous. I live less than a mile from the C/O and I'm getting a ping of 44ms? That is bogus. That means either a)there are very crappy copper lines from my location to the C/O or something is setup poorly on Sprint's end.
I did leave out that there may be a slight chance that my setup is screwy, but I highly doubt it. |
|
| reply to indy0365
newest tracert after fastpath suppose turned on
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 30 ms 30 ms 30 ms oh-69-69-170-1.dhcp.embarqhsd.net [69.69.170.1]
2 54 ms 50 ms 56 ms crohmnfd02 [69.69.33.245]
3 61 ms 62 ms 62 ms sl-gw31-chi-4-1.sprintlink.net [160.81.42.5]
4 61 ms 61 ms 61 ms sl-bb21-chi-4-0.sprintlink.net [144.232.26.29]
5 66 ms 65 ms 64 ms sl-bb22-chi-15-0.sprintlink.net [144.232.26.97]
6 62 ms 62 ms 62 ms sl-st21-chi-11-0.sprintlink.net [144.232.20.21]
7 65 ms 65 ms 66 ms ggr3-p330.cgcil.ip.att.net [192.205.33.157]
8 87 ms 87 ms 87 ms tbr1033301.cgcil.ip.att.net [12.123.4.242]
9 87 ms 88 ms 88 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
10 83 ms 83 ms 83 ms 12.122.84.41
11 89 ms 89 ms 87 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
12 93 ms 94 ms 92 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
13 89 ms 89 ms 88 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
14 88 ms 88 ms 88 ms www.dslreports.com [209.123.109.175]
Trace complete. |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | reply to Techman21
It has nothing to do with network capacity or poor infrastructure. It has everything to do with putting all customer's on interleave and refusing to take them off. |
|
 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2 | I think it's important to point out that Embarq isn't the only DSL provider that is inflexible about reducing the interleaving delay. *COUGH*Qwest*COUGH* |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | People have reported that they were successful in getting Sprint to reduce the interleave delay, which is ok. It would be optimal for them to just remove interleave. |
|
| My ping times to the 1st hop were 46ms, after fastpath turned on, it dropped to 12ms. I consistantly get a ping times of 37ms now to a game server I was getting about 57ms and browsing is snappier. They are testing speed increase of 10mb/1mb, hope they get this released soon, but they are doing the right thing of upgrading their WAN before they release that. |
|
