Meeble
join:2002-09-19
Champaign, IL | Champaign - 8/17 packet loss ?
anyone else in chambana seeing some high latency and packet loss tonight ? |
|
syxxness
join:2005-08-17
Chrisman, IL
| Oh yes of course. I live in chrisman but I connect through the champaign service. In fact I was on the phone with some techs for over 3 hours trying to help them diagnose the problem. As far as I know a ticket has been sent to the main network guys about the problem. After this I wasn't expecting to hear back but to my suprise i recieved phone calls from 3 other techs that night all requesting additional information from me. I should know more later today. |
|
illini25
join:2002-01-19
Urbana, IL | reply to Meeble
I wasn't online last night..but the past few weeks..my ping would shoot up from 30ms to around 400ms or higher any BF2 server that I play on.  |
|
syxxness
join:2005-08-17
Chrisman, IL | i know insight is such bs when it comes to ping times. i'm moving so I can get dsl. |
|
Ripperingo
join:2004-09-02
Champaign, IL
| reply to Meeble
No high pings or packetloss here (westside campus) over the past days/weeks, but since last nights thunderstorm, I'm offline completely. I fear that my cable modem is fried, even though it says it's working fine. I'm about to call insight to see if they have network problems (lightning strike?) |
|
Ripperingo
join:2004-09-02
Champaign, IL
| reply to Meeble
hmm, well, my outage was caused by an overheated network card (it's about to die i guess). I switched lines on my nic's and it works again. However, i had to register the new nic with insight to get on line, and speeds are absolutely in the crapper now (like 33k6 modem-style bad) :( Latency was never better though, strangely enough.
C:\ping 66.165.113.2 -n 15
Pinging 66.165.113.2 with 32 bytes of data:
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=20ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Ping statistics for 66.165.113.2:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 20ms, Average = 18ms |
|
EvilMoose
join:2003-02-26
Urbana, IL | reply to Meeble
*cough*
I wish I got sub 40 pings... I can't even get that to other computers inside our town. |
|
illini25
join:2002-01-19
Urbana, IL
edit:
August 21st, @10:37PM
| said by EvilMoose  :*cough* I wish I got sub 40 pings... I can't even get that to other computers inside our town. Your kidding me right Evil?? Pings have been pretty good over here in Urbana..at least to local servers. Ping this ip for me and see what you get; 146.82.151.56 It's a game server based out of Chicago. I just ran a tracert and pinged 12ms. What hop does it start getting high for you? |
|
Ripperingo
join:2004-09-02
Champaign, IL
edit:
August 22nd, @01:33AM
| reply to Meeble
i play in the server of another clan a lot, it's an 8.9.*.* ip (chi-town), i get an ingame ping of 20, and a tracert shows only 8 or 9 hops from my box to the server :)
My speed trouble i mentioned before was user error btw. Had the NIC set to force 10Mb , put it back to autonegotiate and i'm getting 4.9Mb/s download (on the standard plan).
Illini25's ip:
C:\>ping 146.82.151.56 -n 10
Pinging 146.82.151.56 with 32 bytes of data:
Reply from 146.82.151.56: bytes=32 time=12ms TTL=121
Reply from 146.82.151.56: bytes=32 time=15ms TTL=121
Reply from 146.82.151.56: bytes=32 time=14ms TTL=121
Reply from 146.82.151.56: bytes=32 time=12ms TTL=121
Reply from 146.82.151.56: bytes=32 time=13ms TTL=121
Reply from 146.82.151.56: bytes=32 time=13ms TTL=121
Reply from 146.82.151.56: bytes=32 time=13ms TTL=121
Reply from 146.82.151.56: bytes=32 time=13ms TTL=121
Reply from 146.82.151.56: bytes=32 time=12ms TTL=121
Reply from 146.82.151.56: bytes=32 time=12ms TTL=121
Ping statistics for 146.82.151.56:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 12ms |
|
