Results 511 to 520 of 613
Thread: Tracert's
-
-
Registered TeamPlayer
- Join Date
- 07-22-05
- Location
- Houston
- Posts
- 6,871
- Post Thanks / Like
- Stat Links
-
-
03-15-10, 09:42 PM #513
Re: Tracert's
Seems that lt (layeredtech) your sourcebox host experiences a lot of latency during the evening.
Going to experiment with something, as it seems I am only one of few that are seeing this latency off that edge router.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 9 ms 12 ms te-5-1-ur01.cosprings.co.denver.comcast.net [68.86.129.65]
4 12 ms 12 ms 10 ms te-0-2-0-1-ar02.denver.co.denver.comcast.net [68.86.128.77]
5 14 ms 12 ms 13 ms pos-0-1-0-0-ar02.aurora.co.denver.comcast.net [68.86.128.242]
6 13 ms 11 ms 14 ms pos-0-3-0-0-cr01.denver.co.ibone.comcast.net [68.86.91.1]
7 13 ms 14 ms 18 ms te-4-3.car2.Denver1.Level3.net [4.79.82.53]
8 * 28 ms 18 ms ae-31-53.ebr1.Denver1.Level3.net [4.68.107.94]
9 31 ms 35 ms 36 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 30 ms 28 ms 28 ms ae-2-70.edge3.Dallas1.Level3.net [4.69.145.72]
11 38 ms 31 ms 28 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6]
12 85 ms 84 ms 84 ms dbce10glt.layeredtech.com [66.18.0.142]
13 * * * Request timed out.
14 88 ms 88 ms 90 ms 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
Ping statistics for 72.233.44.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 95ms, Average = 89ms
Edit:
I was correct, it is some sort of source based QoS going on there. The traceroute looks similar but when it actually reaches the destination the latency is back to normal now. (Changed my IP to a different subnet)
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 9 ms te-5-1-ur02.cosprings.co.denver.comcast.net [68.86.129.69]
4 11 ms 11 ms 12 ms te-0-2-0-1-ar02.aurora.co.denver.comcast.net [68.86.128.85]
5 13 ms 11 ms 11 ms pos-0-4-0-0-cr01.denver.co.ibone.comcast.net [68.86.91.101]
6 28 ms 31 ms 22 ms te-4-4.car2.Denver1.Level3.net [4.79.82.57]
7 15 ms 17 ms 18 ms ae-31-53.ebr1.Denver1.Level3.net [4.68.107.94]
8 30 ms 36 ms 35 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
9 28 ms 28 ms 29 ms ae-4-90.edge3.Dallas1.Level3.net [4.69.145.200]
10 87 ms 83 ms 83 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6]
11 91 ms 87 ms 90 ms dbce10glt.layeredtech.com [66.18.0.142]
12 * * * Request timed out.
13 34 ms * 33 ms 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
Ping statistics for 72.233.44.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 31ms, Average = 29ms
-
03-15-10, 09:51 PM #514
Re: Tracert's
In the order they are on the home page.
All servers had 28~ people on them (or full)
Code:tracert 207.210.254.227 Tracing route to 227.254.210.207.hypernia.com [207.210.254.227] over a maximum of 30 hops: 1 <1 ms 1 ms <1 ms 192.168.7.1 2 1 ms 12 ms 12 ms cust-etsu-70-1.mounet.com [216.145.70.1] 3 1 ms 12 ms 12 ms jcrtr01-cust-etsu.mounet.com [216.145.64.205] 4 11 ms 13 ms 11 ms 12.88.84.17 5 12 ms 22 ms 15 ms cr83.attga.ip.att.net [12.122.141.14] 6 12 ms 22 ms 15 ms cr1.attga.ip.att.net [12.123.22.109] 7 11 ms 12 ms 12 ms ggr7.attga.ip.att.net [12.122.87.61] 8 16 ms 15 ms 15 ms 192.205.35.210 9 23 ms 17 ms 18 ms ae-62-51.ebr2.Atlanta2.Level3.net [4.68.103.29] 10 21 ms 17 ms 17 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20] 11 * * 47 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21] 12 36 ms 37 ms 36 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 13 37 ms 37 ms 36 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70] 14 33 ms 37 ms 31 ms 227.254.210.207.hypernia.com [207.210.254.227] Trace complete. tracert 207.210.254.228 Tracing route to 228.254.210.207.hypernia.com [207.210.254.228] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.7.1 2 1 ms 12 ms 15 ms cust-etsu-70-1.mounet.com [216.145.70.1] 3 1 ms 12 ms 12 ms jcrtr01-cust-etsu.mounet.com [216.145.64.205] 4 11 ms 12 ms 12 ms 12.88.84.17 5 12 ms 27 ms 11 ms cr84.attga.ip.att.net [12.122.140.14] 6 12 ms 27 ms 20 ms cr2.attga.ip.att.net [12.123.22.249] 7 11 ms 12 ms 16 ms ggr7.attga.ip.att.net [12.122.82.105] 8 15 ms 21 ms 15 ms 192.205.35.214 9 24 ms 17 ms 17 ms ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62] 10 42 ms 38 ms 35 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21] 11 35 ms 36 ms 36 ms ae-41-90.car1.Dallas1.Level3.net [4.69.145.195] 12 37 ms 36 ms 36 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70] 13 33 ms 32 ms 32 ms 228.254.210.207.hypernia.com [207.210.254.228] Trace complete. tracert 207.210.254.229 Tracing route to 229.254.210.207.hypernia.com [207.210.254.229] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.7.1 2 1 ms 12 ms 12 ms cust-etsu-70-1.mounet.com [216.145.70.1] 3 1 ms 12 ms 12 ms jcrtr01-cust-etsu.mounet.com [216.145.64.205] 4 11 ms 12 ms 12 ms 12.88.84.17 5 14 ms 25 ms 12 ms cr83.attga.ip.att.net [12.122.141.14] 6 12 ms 25 ms 12 ms cr1.attga.ip.att.net [12.123.22.109] 7 11 ms 15 ms 11 ms ggr7.attga.ip.att.net [12.122.82.97] 8 15 ms 16 ms 15 ms 192.205.35.214 9 26 ms 17 ms 17 ms ae-61-51.ebr1.Atlanta2.Level3.net [4.68.103.28] 10 18 ms 18 ms 17 ms ae-63-60.ebr3.Atlanta2.Level3.net [4.69.138.4] 11 42 ms 35 ms 36 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21] 12 36 ms 36 ms 36 ms ae-31-80.car1.Dallas1.Level3.net [4.69.145.131] 13 37 ms 37 ms 37 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70] 14 46 ms 38 ms 38 ms 229.254.210.207.hypernia.com [207.210.254.229] Trace complete. tracert 207.210.254.230 Tracing route to 230.254.210.207.hypernia.com [207.210.254.230] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.7.1 2 1 ms 12 ms 12 ms cust-etsu-70-1.mounet.com [216.145.70.1] 3 1 ms 12 ms 12 ms jcrtr01-cust-etsu.mounet.com [216.145.64.205] 4 11 ms 12 ms 12 ms 12.88.84.17 5 12 ms 24 ms 13 ms cr83.attga.ip.att.net [12.122.141.14] 6 12 ms 24 ms 13 ms cr1.attga.ip.att.net [12.123.22.109] 7 11 ms 12 ms 12 ms ggr7.attga.ip.att.net [12.122.81.241] 8 15 ms 15 ms 15 ms 192.205.35.218 9 15 ms * 28 ms ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62] 10 38 ms 36 ms 36 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21] 11 35 ms 36 ms 36 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 12 36 ms 36 ms 36 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70] 13 32 ms 32 ms 32 ms 230.254.210.207.hypernia.com [207.210.254.230] Trace complete.
-
Registered TeamPlayer
- Join Date
- 02-12-07
- Posts
- 9,210
- Post Thanks / Like
- Stat Links
-
- Gamer IDs
-
03-18-10, 08:57 PM #515Re: Tracert's
Rush Ranked 1
Full server
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Chris>tracert 207.210.254.228
Tracing route to 228.254.210.207.hypernia.com [207.210.254.228]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.1.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms te-8-2-ur02.greenwood.in.indiana.comcast.net [68
.85.177.113]
4 10 ms 8 ms 9 ms te-0-9-0-6-ar01.indianapolis.in.indiana.comcast.
net [68.85.177.26]
5 17 ms 16 ms 15 ms pos-0-14-0-0-ar01.area4.il.chicago.comcast.net [
68.87.231.17]
6 16 ms 16 ms 16 ms pos-1-14-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.90.45]
7 15 ms 16 ms 16 ms xe-9-3-0.edge1.Chicago2.Level3.net [4.71.248.21]
8 15 ms 14 ms 15 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
9 40 ms 39 ms 67 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
10 43 ms 39 ms 50 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
11 * * * Request timed out.
12 50 ms 49 ms 50 ms ae-31-80.car1.Dallas1.Level3.net [4.69.145.131]
13 59 ms 52 ms 61 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
14 51 ms 52 ms * 228.254.210.207.hypernia.com [207.210.254.228]
15 * * 52 ms 228.254.210.207.hypernia.com [207.210.254.228]
Trace complete.
C:\Users\Chris>
So what the fuck does this mean?
So i go from Whiteland, to greenwood, to Indy, to chicago, to denver, to dallas? Jesus christ
-
-
03-19-10, 12:41 AM #517
Re: Tracert's
yes. which on a fiber backbone, is well, at the speed of light. there is some latency due to hardware along those routes, but still, you're looking at what, .052 seconds at your furthest hop?
Originally Posted by Kraker Jak
it's not the distance that that the packet travels. i'm seeing in your tracert that you have packets timing out. you look fine up until hop 14, which is between level3 and hypernia. i would at this point run a 1000 count 1 byte ping test to see how many time out, and then contact your ISP to push that along the chain to them. i'm seeing at least 33% packet failure so far. and that is unacceptable.
-
Registered TeamPlayer
- Join Date
- 02-12-07
- Posts
- 9,210
- Post Thanks / Like
- Stat Links
-
- Gamer IDs
-
03-19-10, 06:38 AM #518Re: Tracert's
Originally Posted by Braddoc
yes. which on a fiber backbone, is well, at the speed of light. there is some latency due to hardware along those routes, but still, you're looking at what, .052 seconds at your furthest hop? Originally Posted by Kraker Jak
it's not the distance that that the packet travels. i'm seeing in your tracert that you have packets timing out. you look fine up until hop 14, which is between level3 and hypernia. i would at this point run a 1000 count 1 byte ping test to see how many time out, and then contact your ISP to push that along the chain to them. i'm seeing at least 33% packet failure so far. and that is unacceptable.
So what can my ISP do about it?
-
Registered TeamPlayer
- Join Date
- 08-16-07
- Posts
- 3,167
- Post Thanks / Like
- Stat Links
-
- Gamer IDs
-
03-19-10, 02:34 PM #519Re: Tracert's
I work for an ISP, and generally we won't do shit. Most of the time if we are having multiple trouble tickets come in we will open a ticket with our interconnect but they will tell us the same as we will tell you....(all tests run fine in our network)....It's almost impossible to get to the large carriers unless there are tons of smaller carriers issuing trouble tickets. ISP's rarely care about latency because the majority of our customers are website browsers or email users. Small packet loss issues to one provider like Hypernia is not our problem. It's the website or providers problem. Originally Posted by Kraker Jak
Originally Posted by Braddoc
yes. which on a fiber backbone, is well, at the speed of light. there is some latency due to hardware along those routes, but still, you're looking at what, .052 seconds at your furthest hop? Originally Posted by Kraker Jak
it's not the distance that that the packet travels. i'm seeing in your tracert that you have packets timing out. you look fine up until hop 14, which is between level3 and hypernia. i would at this point run a 1000 count 1 byte ping test to see how many time out, and then contact your ISP to push that along the chain to them. i'm seeing at least 33% packet failure so far. and that is unacceptable.
So what can my ISP do about it?
It's worth a try to call them, you may not be the only one seeing the problem, but I can almost assure you, your local ISP won't be able to help.
-
Registered TeamPlayer
- Join Date
- 07-22-05
- Location
- Houston
- Posts
- 6,871
- Post Thanks / Like
- Stat Links
-
03-22-10, 09:37 PM #520Re: Tracert's
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Owner>tracert
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.
C:\Users\Owner>ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] [-R] [-S srcaddr] [-4] [-6] target_name
Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet (IPv4-only).
-i TTL Time To Live.
-v TOS Type Of Service (IPv4-only).
-r count Record route for count hops (IPv4-only).
-s count Timestamp for count hops (IPv4-only).
-j host-list Loose source route along host-list (IPv4-only).
-k host-list Strict source route along host-list (IPv4-only).
-w timeout Timeout in milliseconds to wait for each reply.
-R Use routing header to test reverse route also (IPv6-only).
-S srcaddr Source address to use.
-4 Force using IPv4.
-6 Force using IPv6.
C:\Users\Owner>tracert 76.30.30.99
Tracing route to c-76-30-30-99.hsd1.tx.comcast.net [76.30.30.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms c-76-30-30-99.hsd1.tx.comcast.net [76.30.30.99]
Trace complete.
C:\Users\Owner>ping 76.30.30.99
Pinging 76.30.30.99 with 32 bytes of data:
Reply from 76.30.30.99: bytes=32 time<1ms TTL=64
Reply from 76.30.30.99: bytes=32 time<1ms TTL=64
Reply from 76.30.30.99: bytes=32 time<1ms TTL=64
Reply from 76.30.30.99: bytes=32 time<1ms TTL=64
Ping statistics for 76.30.30.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Owner>tracert 207.210.254.227
Tracing route to 227.254.210.207.hypernia.com [207.210.254.227]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 8 ms 5 ms 73.209.216.1
3 7 ms 8 ms 9 ms ge-3-25-ur01.bearcreek.tx.houston.comcast.net [6
8.85.248.121]
4 7 ms 15 ms 6 ms po-15-ar02.bearcreek.tx.houston.comcast.net [68.
85.244.69]
5 17 ms 16 ms 15 ms po-16-ar01.greenspoint.tx.houston.comcast.net [6
8.85.244.73]
6 32 ms 29 ms 29 ms 68.85.245.149
7 8 ms 9 ms 7 ms 68.85.245.246
8 14 ms 14 ms 12 ms te-0-1-0-4-cr01.dallas.tx.ibone.comcast.net [68.
86.91.57]
9 13 ms 13 ms 14 ms xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9]
10 14 ms 14 ms 14 ms ae-31-80.car1.Dallas1.Level3.net [4.69.145.131]
11 43 ms 23 ms 15 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
12 19 ms 15 ms 16 ms 227.254.210.207.hypernia.com [207.210.254.227]
Trace complete.
I pinged Conquest 1 where i tend to play since I bought the game last week.
When there is say 12 to 20 players the server is fine, once we hit say 25 - 32 the server goes to shit for multiple people.
Plus as you can see my tracert pops around a couple times in town locally then heads straight to dallas.
Plus I tested the general health of my connection through multiple servers and my overall speed of connection is above average like usual and my ping is extremely low.
There is a glitch in the matrix somewhere."And the hits just keep on coming." - Tom Cruise, A Few Good Men
View Profile
View Forum Posts
View Forum Threads
Show All Albums
Private Message
View Friends
View Articles
View Blog Entries
Quote
Visit Homepage
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks