Flitterkill January 26, 2006 Share Flitterkill GC Board Member January 26, 2006 Hi! Yep - bit of chop the last month or so - manifesting in not too pleasant lag on Tuesday evening. Worked through this with Tom at Vipers a few hours ago. Not CPU lag - we are barely impacting the CPU Not Bandwidth outbound from the box - again, not even beginning to impact things there However, Tom was seeing not too pleasant packet loss at the Data Center (Equinix in Chicago) and that is prob where we have been getting the chop from - and this has prob been building for the last month or so. So... Our eyes are on it - lets see how soon this clears up EDIT: Prob a combination of Equinix and Sevis lines - being tracked, hang on, this may take a day or two.... -Fk Link to comment Share on other sites More sharing options...
ebits February 1, 2006 Share ebits Member February 1, 2006 I kept getting killed cuz I didn't see what hit me. Link to comment Share on other sites More sharing options...
HWarrior February 9, 2006 Share HWarrior Member February 9, 2006 Traceroute at Feb 9, 2006 5PM EST From my comp Tracing route to 66.90.114.55 over a maximum of 30 hops 1 8 ms 7 ms 8 ms 10.205.128.1 2 11 ms 8 ms 10 ms 68.87.151.169 3 11 ms 8 ms 9 ms 10g-9-1-ur02.cambridge.ma.boston.comcast.net [68.87.144.70] 4 8 ms 9 ms 9 ms 10g-9-2-ur01.malden.ma.boston.comcast.net [68.87.144.73] 5 8 ms 9 ms 9 ms 10g-9-1-ur02.malden.ma.boston.comcast.net [68.87.144.177] 6 9 ms 9 ms 10 ms 10g-8-4-ar01.woburn.ma.boston.comcast.net [68.87.144.173] 7 10 ms 9 ms 10 ms 12.125.47.17 8 15 ms 15 ms 16 ms gbr2-p10.cb1ma.ip.att.net [12.123.40.190] 9 17 ms 17 ms 19 ms tbr1-p013702.cb1ma.ip.att.net [12.122.5.61] 10 17 ms 17 ms 18 ms tbr2-cl16.n54ny.ip.att.net [12.122.10.22] 11 15 ms 15 ms 15 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62] 12 15 ms 16 ms 15 ms nyk-b2-link.telia.net [213.248.83.97] 13 16 ms 15 ms 16 ms nyk-bb1-pos1-2-0.telia.net [213.248.80.77] 14 36 ms 37 ms 36 ms chi-bb1-pos6-0-0-0.telia.net [213.248.80.153] 15 49 ms 49 ms 48 ms rcn-112386-chi-bb1.c.telia.net [213.248.84.90] 16 49 ms 49 ms 47 ms . [66.90.127.254] 17 48 ms 45 ms 46 ms 66.90.114.55 Trace complete. From server in Texas (better path going datacenter to datacenter) traceroute to 66.90.114.55 (66.90.114.55), 30 hops max, 38 byte packets 1 ev1s-216-127-88-1.ev1servers.net (216.127.88.1) 0.496 ms 0.340 ms 0.276 ms 2 ivhou-207-218-245-4.ev1.net (207.218.245.4) 0.365 ms 0.422 ms 0.391 ms 3 ivhou-207-218-223-11.ev1.net (207.218.223.11) 0.709 ms 0.417 ms 0.458 ms 4 64.245.101.53 (64.245.101.53) 1.649 ms 1.567 ms 1.440 ms 5 p3-0-0.MAR2.Houston4-TX.us.xo.net (71.5.180.205) 1.667 ms 1.751 ms 1.653 ms 6 p4-1-0.RAR2.Dallas-TX.us.xo.net (65.106.4.205) 7.260 ms 7.366 ms 7.541 ms 7 p1-0.IR1.Dallas2-TX.us.xo.net (65.106.4.186) 7.112 ms 7.147 ms 7.189 ms 8 206.111.5.54.ptr.us.xo.net (206.111.5.54) 7.175 ms 6.999 ms 7.076 ms 9 p13-0.core02.dfw01.atlas.cogentco.com (154.54.2.137) 7.307 ms 8.144 ms 7.624 ms 10 p15-0.core01.mci01.atlas.cogentco.com (66.28.4.38) 16.382 ms 16.627 ms 16.607 ms 11 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 27.891 ms 28.006 ms 28.398 ms 12 g0-1.na21.b000268-0.ord01.atlas.cogentco.com (66.28.6.14) 28.152 ms 28.356 ms 28.082 ms 13 FDCServersNet.demarc.cogentco.com (38.112.26.66) 28.735 ms 29.391 ms 29.063 ms 14 . (66.90.127.254) 29.444 ms 33.689 ms 35.380 ms 15 66.90.114.55 (66.90.114.55) 30.987 ms 30.783 ms 31.592 ms Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now