Today's Lag

**Rogean** · #1 09-09-2014, 05:19 PM

Can some of you post trace routes. I think it's an issue with an upstream provider (GTT?).

Awwalike · #2 09-09-2014, 05:21 PM

i think nizzar hired toop brah

cimarron · #3 09-09-2014, 05:23 PM

From comcast. Seems to be GTT.

1 <1 ms <1 ms <1 ms [192.168.1.1]
2 7 ms 7 ms 8 ms 73.115.226.1
3 9 ms 9 ms 7 ms 68.85.164.97
4 10 ms 11 ms 11 ms 162-151-54-37-static.hfc.comcastbusiness.net [162.151.54.37]
5 20 ms 18 ms 20 ms he-1-13-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.94.81]
6 * * * Request timed out.
7 18 ms 17 ms 18 ms ae12.chi11.ip4.gtt.net [199.229.229.249]
8 39 ms 39 ms 39 ms xe-10-2-2.nyc41.ip4.gtt.net [141.136.111.62]
9 71 ms * 72 ms gtt-gw.ip4.gtt.net [199.229.230.94]
10 67 ms 67 ms * as20473.ae2.ar2.ewr1.us.as4436.gtt.net [69.31.34.210]
11 * 68 ms 66 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.80.26]
12 69 ms 68 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
13 66 ms 67 ms 67 ms rogean.com [108.61.129.165]

GinnasP99 · #4 09-09-2014, 05:26 PM

^ Don't worry lads, We've got top men on it. Top men.

Rec · #5 09-09-2014, 05:27 PM

From Comcast

Tracing route to rogean.com [108.61.129.165]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms *****
2 28 ms 29 ms 29 ms *****
3 38 ms 19 ms 12 ms te-4-2-ur01.swedesboro.nj.panjde.comcast.net [68
.85.116.197]
4 10 ms 10 ms 10 ms te-9-3-ur02.woodbury.nj.panjde.comcast.net [68.8
5.35.133]
5 10 ms 10 ms 11 ms te-9-3-ur01.woodbury.nj.panjde.comcast.net [68.8
5.35.129]
6 12 ms 11 ms 14 ms xe-18-0-6-0-ar03.audubon.nj.panjde.comcast.net [
68.86.210.97]
7 15 ms 15 ms 15 ms 68.86.166.109
8 14 ms 14 ms 14 ms 23.30.207.94
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 19 ms 19 ms 19 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]

13 19 ms 21 ms 21 ms CHOOPA-LLC.edge3.NewYork1.Level3.net [4.31.21.58
]
14 18 ms 18 ms 22 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.80.26]
15 20 ms 20 ms 18 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
16 20 ms 20 ms 19 ms rogean.com [108.61.129.165]

phacemeltar · #6 09-09-2014, 05:28 PM

9 20 ms 21 ms 20 ms ae14.ar1.ord1.us.as4436.gtt.net [69.31.111.113]
10 18 ms 16 ms 17 ms ae1-70g.cr2.ord1.us.as4436.gtt.net [69.31.111.137]
11 20 ms 20 ms 19 ms ae3-60g.cr1.ord1.us.as4436.gtt.net [69.31.111.153]
12 38 ms 41 ms 38 ms xe-0-0-0.cr2.iad1.us.as4436.gtt.net [69.22.142.189]
13 43 ms 38 ms 38 ms ae1-50g.cr1.iad1.us.as4436.gtt.net [69.31.31.153]
14 44 ms 43 ms 43 ms xe-0-0-0.cr1.phl1.us.as4436.gtt.net [69.22.142.163]
15 55 ms 53 ms 54 ms phi12.ip4.gtt.net [173.205.62.137]
16 61 ms 66 ms 74 ms xe-10-1-0.nyc39.ip4.gtt.net [89.149.181.193]
17 115 ms 106 ms 94 ms ae10-69.cr1-nyc3.ip4.gtt.net [46.33.80.234]
18 96 ms 98 ms 97 ms ae1-50g.ar1.nyc3.us.as4436.gtt.net [69.31.95.194]
19 103 ms 98 ms 97 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34.62]
20 96 ms 96 ms 96 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
21 98 ms 104 ms 98 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
22 95 ms 57 ms 96 ms rogean.com [108.61.129.165]

Trace complete.

Sajan · #7 09-09-2014, 05:28 PM

Quote:

tracert project1999.com

Tracing route to project1999.com [108.61.129.170]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms home [192.168.1.254]
2 9 ms 10 ms 12 ms adsl-98-80-9-1.shv.bellsouth.net [98.80.9.1]
3 20 ms 20 ms 20 ms 72.157.35.103
4 20 ms 20 ms 22 ms 12.81.102.72
5 20 ms 20 ms 20 ms 12.81.102.47
6 20 ms 20 ms 20 ms 65.83.239.126
7 21 ms 20 ms 22 ms 12.81.82.105
8 24 ms 22 ms 22 ms 12.81.104.138
9 20 ms 20 ms 22 ms 12.81.24.29
10 20 ms 20 ms 20 ms 74.175.192.46
11 36 ms 34 ms 34 ms cr2.nwrla.ip.att.net [12.123.153.82]
12 35 ms 36 ms 34 ms gbr3.sl9mo.ip.att.net [12.122.2.145]
13 37 ms 34 ms 34 ms 12.122.141.233
14 * * * Request timed out.
15 * 54 ms 56 ms xe-1-2-2.nyc41.ip4.gtt.net [141.136.110.221]
16 55 ms * 57 ms gtt-gw.ip4.gtt.net [199.229.230.94]
17 56 ms 66 ms 55 ms as20473.ae2.ar2.ewr1.us.as4436.gtt.net [69.31.34
.210]
18 58 ms 55 ms 57 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.80.26]
19 57 ms 55 ms 55 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
20 56 ms 55 ms 55 ms 170.rogean.com [108.61.129.170]

Trace complete.

Aveenia · #8 09-09-2014, 05:30 PM

From Comcast in TN

Tracing route to rogean.com [108.61.129.165]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 41 ms 29 ms 29 ms 71.203.232.1
3 24 ms 11 ms 11 ms 68.86.151.21
4 12 ms 16 ms 22 ms xe-1-1-1-0-ar01.goodslettvll.tn.nash.comcast.net
[162.151.9.126]
5 26 ms 19 ms 21 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net
[68.86.90.101]
6 19 ms * 19 ms 23.30.207.98
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 37 ms 37 ms 34 ms ae-2-52.edge3.Newark1.Level3.net [4.69.156.43]
11 147 ms * 144 ms CHOOPA-LLC.edge3.Newark1.Level3.net [4.35.16.58]

12 * * * Request timed out.
13 141 ms 139 ms * vl203-cr1.ewr3.choopa.net [216.155.128.2]
14 * * * Request timed out.
15 153 ms * 147 ms rogean.com [108.61.129.165]

Trace complete.

**Rogean** · #9 09-09-2014, 05:30 PM

Quote:

Hi Sean,

Thank you for reaching out to us.

Our network engineers have been actively investigating this top priority issue with relevant upstream providers and peers. Performance has been steadily improving and we are expecting a root cause analysis at some point in the future. Thank you for your cooperation and patience as we work to ensure optimal performance.

Regards,
Marco Vescio
System Administrator

Top Men indeed.

Awwalike · #10 09-09-2014, 05:36 PM

just googled Marco Vescio, looks like a turd