dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5
share rss forum feed


ILpt4U
Premium
join:2006-11-12
Lisle, IL
kudos:9
Reviews:
·AT&T U-Verse
reply to Darknessfall

Re: fastpath

said by Darknessfall:

@ILpt4U

Didn't know ADSL2+ could be on fast path. Thanks for clearing that up for me .

Used to be that almost all ADSL2+ orders I did were fast path (and when I had ADSL2+ U-Verse mine was fast path as well), but lately most of the orders are set on interleave.

The change might have something to do with the ADSL2+ VoIP offering I'm thinking, because that was about the time I noticed the general shift from defaulting fast path to defaulting interleave

That being said, fast path does still exist on ADSL2+ U-Verse

gladia7or

join:2013-01-17
Jacksonville, FL
Tracing route to host.colocrossing.com [198.144.179.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 31 ms 20 ms 20 ms 108-65-160-3.lightspeed.jcvlfl.sbcglobal.net [10
8.65.160.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 19 ms 19 ms 70.159.204.190
7 34 ms 25 ms 24 ms 12.81.50.30
8 32 ms 25 ms 25 ms 12.81.105.104
9 31 ms 30 ms 26 ms 12.83.22.190
10 26 ms 24 ms 24 ms 12.81.28.45
11 119 ms 26 ms 72 ms 74.175.192.10
12 31 ms 31 ms 32 ms cr2.ormfl.ip.att.net [12.122.106.70]
13 34 ms 33 ms 30 ms cr81.fldfl.ip.att.net [12.122.1.46]
14 33 ms 32 ms 31 ms 12.122.155.169
15 43 ms 42 ms 43 ms 192.205.32.142
16 52 ms 51 ms 51 ms 144.232.6.12
17 58 ms 57 ms 57 ms 144.232.5.213
18 73 ms 73 ms 72 ms 144.232.25.217
19 72 ms 71 ms 72 ms sl-crs1-chi-0-0-0-1.sprintlink.net [144.232.24.4
6]
20 72 ms 74 ms 72 ms 144.232.1.102
21 74 ms 74 ms * sl-nlaye-467201-0.sprintlink.net [144.223.73.210
]
22 72 ms 71 ms 84 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
23 71 ms 71 ms 71 ms as23352.ae6-101.cr1.ord1.us.nlayer.net [69.31.11
1.1]
24 72 ms 72 ms 72 ms ae11.cr1.ord6.us.scnet.net [204.93.204.73]
25 76 ms 73 ms 73 ms ae3.ar6.ord6.us.scnet.net [204.93.204.49]
26 72 ms 72 ms 72 ms as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
27 72 ms 73 ms 73 ms 10ge-1-3-1.fz146.cr1.chi.colocrossing.com [206.2
17.130.114]
28 73 ms 72 ms 76 ms host.colocrossing.com [205.234.152.250]
29 72 ms 71 ms 72 ms host.colocrossing.com [198.144.179.110]

My friend down the road has comcast and pings 40 to the same server. I had dsl about a hundred miles south(further from the servers) and pinged around 50-60 as well to these servers. Its not just this server, it is across the board. the timed out pings may be of note.


ILpt4U
Premium
join:2006-11-12
Lisle, IL
kudos:9
Reviews:
·AT&T U-Verse
a difference of 50-60 vs 70 is barely perceivable, if at all. And those are round-trip pings. The one way ping is half that, 25-30 vs 35 -- .005 seconds is not that much different

The time outs on the route are very common -- many routers along the way simply do not respond to the tracert requests, as it is low priority (from what I've read around here) -- that is not indicative of a problem

The routing/peering point in South Florida/Ft Lauderdale is interesting, as the connection goes South from Jacksonville before turning around to go back North..

That being said, it looks like the biggest latency jumps are hops 14-16 (AT&T-Sprint peer), and hops 17-18 (inside Sprint's network)

My latency is a lot lower to the server, but then again it seems to be a Chicago area server, and that is where I am...

Tracing route to host.colocrossing.com [198.144.179.110]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.254
2 67 ms 24 ms 24 ms 108-83-xxx-xxx.lightspeed.cicril.sbcglobal
8.83.xxx.xxx]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 25 ms 27 ms 12.83.43.13
7 25 ms 26 ms 25 ms cgcil02jt.ip.att.net [12.122.81.21]
8 53 ms 26 ms 29 ms 144.232.25.149
9 29 ms 27 ms 28 ms sl-st30-chi-0-0-3-0.sprintlink.net [144.
2]
10 30 ms 26 ms * sl-nlaye-467201-0.sprintlink.net [144.22
]
11 26 ms 25 ms 26 ms ae2-40g.cr2.ord1.us.nlayer.net [69.31.11
12 26 ms 25 ms 26 ms as23352.ae6-102.cr2.ord1.us.nlayer.net [
1.3]
13 27 ms 30 ms 26 ms ae4.cr2.ord6.us.scnet.net [204.93.204.87
14 27 ms 28 ms 30 ms ae4.ar5.ord6.us.scnet.net [204.93.204.65
15 27 ms 26 ms 26 ms as36352.xe-2-0-2.ar5.ord6.us.scnet.net [
1.170]
16 27 ms 28 ms 26 ms 10ge-1-3-2.fz146.cr2.chi.colocrossing.co
17.137.254]
17 31 ms 26 ms 29 ms host.colocrossing.com [205.234.152.250]
18 28 ms 26 ms 26 ms host.colocrossing.com [198.144.179.110]


ILpt4U
Premium
join:2006-11-12
Lisle, IL
kudos:9
Reviews:
·AT&T U-Verse
reply to gladia7or
I also tried tracing back to your VHO's IP (108-65-160-3.lightspeed.jcvlfl.sbcglobal.net [108.65.160.3) and go to 12.81.50.31 in 65 ms, but almost every hop was a time out, because that route is all AT&T, and many of the AT&T points do not respond to the tracert packets

That being said, the route you posted to your game server, peering over sprint, is a quicker route than an all AT&T route, because had I made it all the way to your modem, there would be the 20-25 ms of VDSL2 interleave tacked on, making the total latency somewhere around 90 ms

If the 70 ms of round trip latency is too much, I would have to recommend either trying to get onto ADSL2+ U-Verse with fast path or traditional AT&T ADSL with fast path, or an xDSL reseller in the area (if one is available), or going with another provider

Competitive FPS every ms does matter -- that is probably one of the most sensitive to latency situations out there (that and stock day traders) -- Depending if money is at stake & how much, and how serious a gamer you are, you might even explore metro Ethernet fiber connections from either AT&T or your cable company, but that would probably run a few hundred, if not a few grand, per month. But fiber Ethernet would put your (first hop) pings at darn near zero

gladia7or

join:2013-01-17
Jacksonville, FL
i used to ping mid 20s to Georgia. with this uverse i ping upper 50s, even though i am closer geographically to the server(i know it doesnt matter with routing but still).

am i out of luck with uverse? is there a way i can go back to the other dsl? cable in the area is quite good but i wanted to make it work with uverse.


ILpt4U
Premium
join:2006-11-12
Lisle, IL
kudos:9
Reviews:
·AT&T U-Verse
Only hope with a U-Verse branded product would be to see if you could be switched to ADSL2+ U-Verse, or move to an area/neighborhood served with BPON/GPON/Fiber U-Verse.

Even changing to ADSL2+ U-Verse, you'll still have the South Florida routing, but first hop latency should be a teens number, not a 20s number

Otherwise you would need non-U-Verse xDSL from either AT&T or an xDSL reseller, or shop from the cable company

VDSL2 U-Verse is always interleave. period.