Today's Lag - Page 3

HotRatz · #21 09-09-2014, 08:30 PM

i was in cb lvl 17 and all of a sudden everything started to aggro me...pawns low lvl cents....i ran to the zone and it said loading and froze...logged back in and i was dead and lost my lvl....same thing happened when i logged back in....there is a serious issue going on right now the whole server was frozen or dead from what i saw.

cuffed · #22 09-09-2014, 08:34 PM

I'm using Verizon. During lag I noticed the traceroute go via Level 3 (so Verizon -> Level 3). Now it is going via GTT.. so Verizon -> GTT.

I guess your host (Choopa?) changed who its route is being advertised to for whatever reason. Haven't looked into it too much.

Wiery · #23 09-09-2014, 08:37 PM

This is the second trace. The first had more timeouts, but I wasn't logging.

Code:

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

  1    <1 ms    <1 ms    <1 ms  x
  2    <1 ms    <1 ms    <1 ms  192.10 
  3    19 ms    19 ms    21 ms  104-10-168-2.lightspeed.irvnca.sbcglobal.net [104.10.168.2] 
  4    19 ms    19 ms    19 ms  75.20.1.0 
  5    22 ms    19 ms    19 ms  12.83.38.145 
  6    22 ms    23 ms    23 ms  ggr2.la2ca.ip.att.net [12.122.128.101] 
  7    21 ms    21 ms    21 ms  ae7.lax21.ip4.gtt.net [199.229.231.29] 
  8   186 ms   188 ms   189 ms  xe-1-3-1.nyc41.ip4.gtt.net [141.136.110.141] 
  9   225 ms     *        *     gtt-gw.ip4.gtt.net [199.229.230.94] 
 10     *        *        *     Request timed out.
 11     *      127 ms   126 ms  ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.80.26] 
 12     *      126 ms     *     vl203-cr1.ewr3.choopa.net [216.155.128.2] 
 13   126 ms   126 ms   126 ms  rogean.com [108.61.129.165] 

Trace complete.

kgrenier · #24 09-09-2014, 08:40 PM

Here is my result from Comcast in MA. Problem started last night and is much worse tonight.

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

1 3 ms 1 ms 1 ms 192.168.2.1
2 11 ms 38 ms 11 ms 96.120.65.137
3 9 ms 19 ms 19 ms te-0-1-0-1-sur01.roxbury.ma.boston.comcast.net [
68.85.142.169]
4 16 ms 11 ms 15 ms be-98-ar01.needham.ma.boston.comcast.net [68.85.
106.13]
5 44 ms 45 ms 53 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
6 * * * Request timed out.
7 40 ms 41 ms 43 ms ae3.nyc38.ip4.gtt.net [199.229.230.113]
8 42 ms 40 ms 40 ms xe-10-1-3.nyc41.ip4.gtt.net [141.136.106.222]
9 42 ms 39 ms 48 ms gtt-gw.ip4.gtt.net [199.229.230.94]
10 43 ms 39 ms 47 ms as20473.ae2.ar2.ewr1.us.as4436.gtt.net [69.31.34
.210]
11 45 ms 39 ms 45 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.80.26]
12 42 ms 40 ms 39 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
13 42 ms 39 ms 38 ms rogean.com [108.61.129.165]

Trace complete.

ripwind · #25 09-09-2014, 08:43 PM

TWC. Seems to be fine. Had no issues last night.

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 16 ms 8 ms 8 ms 104.139.224.1
3 9 ms 9 ms 8 ms tge7-6.oshkwi1102h.midwest.rr.com [24.164.234.245]
4 13 ms 15 ms 15 ms tge1-3-0-9.gnfdwibb01r.midwest.rr.com [65.29.46.74]
5 17 ms 15 ms 27 ms ae-6-0.cr0.chi10.tbone.rr.com [66.109.6.204]
6 * * 14 ms ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
7 19 ms 15 ms 30 ms xe-3-0-3.ar2.ord1.us.as4436.gtt.net [69.31.111.125]
8 15 ms 14 ms 14 ms ae2-40g.cr2.ord1.us.as4436.gtt.net [69.31.111.149]
9 40 ms 40 ms 44 ms xe-1-0-0.cr1.iad1.us.as4436.gtt.net [69.22.142.33]
10 71 ms 102 ms 41 ms xe-0-0-0.cr1.phl1.us.as4436.gtt.net [69.22.142.163]
11 47 ms 46 ms 48 ms phi12.ip4.gtt.net [173.205.62.137]
12 49 ms 64 ms 49 ms xe-10-3-6.nyc41.ip4.gtt.net [141.136.110.138]
13 44 ms 46 ms 75 ms ae5-69.cr1.ewr1.ip4.gtt.net [46.33.95.30]
14 43 ms 46 ms 46 ms ae1-70g.ar2.ewr1.us.as4436.gtt.net [69.31.94.118]
15 46 ms 46 ms 49 ms as20473.ae2.ar2.ewr1.us.as4436.gtt.net [69.31.34.210]
16 43 ms 43 ms 42 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.80.26]
17 135 ms 66 ms 50 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 42 ms 46 ms 59 ms rogean.com [108.61.129.165]

yevea · #26 09-09-2014, 08:45 PM

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\c>tracert project1999.org

Tracing route to project1999.org [108.61.129.165]
over a maximum of 30 hops:

1 * * * Request timed out.
2 25 ms 23 ms 21 ms 75-12-92-2.lightspeed.gdrpmi.sbcglobal.net [75.1
2.92.2]
3 * * * Request timed out.
4 22 ms 23 ms 23 ms 12.83.33.129
5 25 ms 27 ms 27 ms ggr4.cgcil.ip.att.net [12.122.133.33]
6 * * * Request timed out.
7 44 ms 43 ms 45 ms vl-3506-ve-120.ebr1.Chicago2.Level3.net [4.69.15
8.134]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 44 ms 44 ms 48 ms ae-1-60.edge1.NewYork1.Level3.net [4.69.155.14]

13 206 ms * * CHOOPA-LLC.edge1.NewYork1.Level3.net [4.78.132.9
8]
14 * 306 ms * ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.80.26]
15 * * * Request timed out.
16 * * * Request timed out.
17 304 ms * * rogean.com [108.61.129.165]
18 * * * Request timed out.
19 210 ms * * rogean.com [108.61.129.165]
20 * * 307 ms rogean.com [108.61.129.165]

Trace complete.

C:\Users\c>ping project1999.org

Pinging project1999.org [108.61.129.165] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 108.61.129.165:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

AT&T Michigan. I've had some success, but it randomly does this to me.

Rika · #27 09-09-2014, 09:21 PM

This is the 1st one I took. From UK. It is spiky though, I get completely different results each tracert.

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

1 21 ms 98 ms 97 ms dsldevice.lan [192.168.1.2
2 18 ms 17 ms 18 ms host-78-148-96-1.as13285.n
3 23 ms 22 ms 23 ms xe-11-2-0-bragg001.bre.as1
9]
4 22 ms 23 ms 23 ms host-78-151-225-124.static
25.124]
5 30 ms 29 ms 30 ms host-78-144-8-33.as13285.n
6 30 ms 29 ms 29 ms host-78-144-10-220.as13285
7 29 ms 29 ms 29 ms ae3-310.lon11.ip4.gtt.net
8 158 ms 96 ms 100 ms xe-2-1-3.nyc39.ip4.gtt.net
9 95 ms 95 ms 95 ms gtt-gw.ip4.gtt.net [173.24
10 96 ms 98 ms 95 ms ae1-50g.ar1.nyc3.us.as4436
]
11 97 ms 96 ms 97 ms as20473.ae7.ar1.nyc3.us.as
.62]
12 139 ms 148 ms 146 ms ethernet1-2-2-c8-12-b2-1.p
.80.218]
13 145 ms 142 ms * vl203-cr1.ewr3.choopa.net
14 * * * Request timed out.
15 * * * Request timed out.
16 144 ms 147 ms 143 ms rogean.com [108.61.129.165

Juevento · #28 09-09-2014, 09:43 PM

Comcast - Seattle, WA

tracert project1999.org

Tracing route to project1999.org [108.61.129.165]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms One.hsd1.wa.comcast.net [192.168.1.1]
2 * * * Request timed out.
3 20 ms 10 ms 11 ms te-0-2-0-10-ur08.seattle.wa.seattle.comcast.net
[68.85.144.153]
4 12 ms 11 ms 11 ms ae-20-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.129]
5 14 ms 14 ms 12 ms he-1-3-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.93.165]
6 29 ms 26 ms 30 ms he-0-13-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.162]
7 34 ms 34 ms 38 ms pos-0-4-0-0-pe01.11greatoaks.ca.ibone.comcast.ne
t [68.86.87.150]
8 33 ms 34 ms 32 ms xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165]
9 116 ms 117 ms 112 ms xe-0-2-2.nyc39.ip4.gtt.net [141.136.106.138]
10 * 134 ms 131 ms gtt-gw.ip4.gtt.net [173.241.131.238]
11 133 ms 136 ms 133 ms ae1-50g.ar1.nyc3.us.as4436.gtt.net [69.31.95.194
]
12 157 ms * 158 ms as20473.ae7.ar1.nyc3.us.as4436.gtt.net [69.31.34
.62]
13 155 ms 155 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61
.80.218]
14 157 ms * 167 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
15 * * 157 ms rogean.com [108.61.129.165]

Trace complete.

HtotheK · #29 09-09-2014, 09:51 PM

Quote:

2 * * * Request timed out.
3 * * * Request timed out.
4 30 ms 32 ms 30 ms 12.83.102.17
5 42 ms 39 ms 40 ms 12.122.157.6
6 39 ms 38 ms 39 ms 12.122.29.53
7 37 ms 37 ms 70 ms 192.205.36.122
8 163 ms 163 ms 161 ms 141.136.108.153
9 164 ms 165 ms 163 ms 173.241.131.238
10 64 ms 62 ms * 69.31.95.194
11 61 ms 62 ms 61 ms 69.31.34.62
12 61 ms 61 ms 60 ms 108.61.80.218
13 166 ms 168 ms 168 ms 216.155.128.2
14 62 ms 62 ms 62 ms 108.61.129.165

PurpleSK · #30 09-09-2014, 10:06 PM

$ 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 192.168.1.1
2 * * * Request timed out.
3 11 ms 8 ms 9 ms dtr03knwcwa-tge-0-4-0-9.knwc.wa.charter.com [96.34.106.145]
4 14 ms 10 ms 21 ms dtr01yakmwa-bue-3.yakm.wa.charter.com [96.34.105.162]
5 17 ms 12 ms 26 ms bbr01yakmwa-bue-1.yakm.wa.charter.com [96.34.105.230]
6 39 ms 39 ms 39 ms bbr02snjsca-bue-3.snjs.ca.charter.com [96.34.2.148]
7 40 ms 31 ms 38 ms prr01snjsca-bue-6.snjs.ca.charter.com [96.34.3.3]
8 37 ms 34 ms 37 ms 96-34-154-98.static.unas.ca.charter.com [96.34.154.98]
9 * 61 ms 32 ms ae0-110g.cr1.sjc1.us.as4436.gtt.net [69.22.143.117]
10 61 ms 33 ms 34 ms ae1-70g.cr1.pao1.us.as4436.gtt.net [69.22.143.166]
11 41 ms 34 ms 53 ms ae5-69.pao10.ip4.gtt.net [77.67.68.201]
12 105 ms 97 ms 98 ms xe-10-3-5.nyc41.ip4.gtt.net [141.136.105.37]
13 98 ms 98 ms 98 ms ae5-69.cr1.ewr1.ip4.gtt.net [46.33.95.30]
14 98 ms 98 ms 101 ms ae1-70g.ar2.ewr1.us.as4436.gtt.net [69.31.94.118]
15 98 ms 98 ms 140 ms as20473.ae2.ar2.ewr1.us.as4436.gtt.net [69.31.34.210]
16 120 ms 100 ms 98 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.80.26]
17 102 ms 97 ms 112 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
18 102 ms 101 ms 100 ms 170.rogean.com [108.61.129.170]

Trace complete.