[UPDATE Below: problem seems to be solved now, no more help needed.]

I'm having trouble with the server again today, and I need to find out if it's just my problem or more universal. So please help me out by doing the following: Open a DOS box, and type "ping -n 100 mee.nu" and when it's complete (which could take five minutes), copy the last four lines of the report into a comment here. It would look like this:

Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 71, Lost = 29 (29% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 98ms, Average = 81ms

Depending on when I do it, I've been running anything from 5-30% lost pings, and I think the reason I'm having trouble is because of failed handshakes. The question is whether it's a Comcast problem or a mee.nu problem.

UPDATE 1455 PDT: According to my pingplot, someone changed something about 15 minutes ago and I went from about 95% lost packets to about 2% lost packets, and now I can get back in again. (For a while there, around noon, I was at a dead 100% lost packets.)

We won't be needing any more reports from anyone, and thanks for the help. Apparently they figured out what was wrong and fixed it.

UPDATE: Well, actually more like 20% lost on my most recent 100 pings, but that's still a hell of a lot better than it was. Check this out:

UPDATE: I just did 100 pings and got 100 responses. 0% loss; that's more like it!

Posted by: Steven Den Beste in Site Stuff at 08:53 AM | Comments (27) | Add Comment
Post contains 258 words, total size 2 kb.

1 If people could also add their internet provider and state, that would be very useful in tracking down the problem.

Posted by: Pixy Misa at June 11, 2007 09:01 AM (PiXy!)

2

Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 68ms, Average = 46ms

Also Comcast from Richmond, VA around 1 pm EST

Posted by: CAL at June 11, 2007 09:09 AM (pXXSx)

3 Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 57ms, Maximum = 62ms, Average = 57ms

twtelecom.net, Seattle WA

Posted by: Cadrys at June 11, 2007 09:28 AM (eYKMM)

4 I seem to be having problems copying from the command prompt, so I'm going to type this out.

Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 72ms, Average = 47ms

I'm using Fidelity Communications in Missouri at about 12:30 central time.

Posted by: Cyndane at June 11, 2007 09:30 AM (pKW2r)

5 From xo.net, Oakland, CA:

Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum =  70ms, Average =  48ms

From covad.net, Oakland, CA (OpenBSD system):

--- mee.nu ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 49.891/59.955/192.932/13.964 ms

Posted by: bloatboy at June 11, 2007 09:31 AM (jTiZc)

6 Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 41ms, Maximum = 57ms, Average = 45ms

Comcast, Monroe, MI

Posted by: demented_42 at June 11, 2007 09:34 AM (TdMIr)

7

Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 88ms, Average = 53ms

From Phoenix, AZ via XO network

Would traceroutes be useful?

Posted by: bkw at June 11, 2007 09:49 AM (bRLba)

8 OK, thanks; I think that's enough. It looks like this is a Comcast problem, and I'll have to get onto Comcast's tech support about it. I can't access this site directly right now at all; I'm running 70% losses on pings. But I'm able to get in easily using a proxy, which is why my IP hash is different.

Posted by: Steven Den Beste at June 11, 2007 09:54 AM (aTZaE)

9 Or maybe not. Pixy is having problems, too. If you do this and get 100% we don't need to hear about it, but if there's anyone else having problems, please let us know.

Posted by: Steven Den Beste at June 11, 2007 10:02 AM (aTZaE)

10 Well, here's from my server at the Infinity Internet hosting facility (Linux ping, big fat hosting pipe): --- mee.nu ping statistics --- 100 packets transmitted, 100 received, 0% packet loss, time 99082ms rtt min/avg/max/mdev = 67.818/69.800/83.695/2.105 ms, pipe 2 The story's entirely different from my office (Windows ping, Comcast business-class broadband): Ping statistics for 75.126.89.164: Packets: Sent = 100, Received = 29, Lost = 71 (71% loss), Approximate round trip times in milli-seconds: Minimum = 77ms, Maximum = 84ms, Average = 80ms Portland OR, both cases.

Posted by: GreyDuck at June 11, 2007 10:12 AM (7eLDR)

11 I was getting 97% packet loss just now, and from the traceroutes the problem was somewhere in Dallas, just outside our hosting company's network.

Because of the problem, I couldn't even reach the support site to log a fault.

Then suddenly everything started working, at least sort of.

Posted by: Pixy Misa at June 11, 2007 10:33 AM (PiXy!)

12

I just saw a 2% loss, but I don't know who is the provider here at work.

Posted by: Will at June 11, 2007 10:39 AM (SOx9v)

13 They're not having storms in Dallas again, are they?  Anyway, I have some servers just up the road and those ones are fine.

Since I couldn't reach the hosting company's support site, I posted a message on their forums.  Now I can reach the support site, but can't reach the forums.

Both mee.nu and mu.nu seem to be happy right now, so I'm off to take a short nap.

(It's 4:30 AM here in Sydney.)

Posted by: Pixy Misa at June 11, 2007 10:42 AM (PiXy!)

14 Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 60ms, Average = 58ms

Earthlink from San Francisco CA 11:50am

Posted by: Toren at June 11, 2007 10:54 AM (/XsVH)

15 My hosting company got back to me - apparently there's a routing issue between Comcast and Global Crossing.  They are poking the engineers involved with pointy objects.  As all you engineers know, that's what they do when you are busy trying to fix something.

Posted by: Pixy Misa at June 11, 2007 10:55 AM (PiXy!)

16 And now I'm really going to bedzzzzzzzzz

Posted by: Pixy Misa at June 11, 2007 10:55 AM (PiXy!)

17 Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 31ms, Average = 20ms

In Houston, Texas.  We're changing from Roadrunner to Comcast and my bills now come from Comcast.  I guess the best thing to tell you is probably that my current IP is 70.114.245.*

Bob Price

Posted by: Bob Price at June 11, 2007 11:02 AM (gHP37)

18

Hoping it won't be redundant...

Statistiche Ping per 75.126.89.164:
    Pacchetti: Trasmessi = 100, Ricevuti = 99, Persi = 1 (1% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
    Minimo = 161ms, Massimo =  300ms, Medio =  210ms

ISP Fastwbenet.it (Italy), 19:08 UTC

Posted by: FabioC. at June 11, 2007 11:08 AM (Lx9ty)

19 Ping statistics for 75.126.89.164: Packets: Sent = 100, Received = 99, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 82ms, Average = 53ms

Posted by: dave talbot at June 11, 2007 11:20 AM (+/3co)

20 OK, I don't think we need any more help. Thanks, everyone!

Posted by: Steven Den Beste at June 11, 2007 11:26 AM (aTZaE)

21 --- mee.nu ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 106336ms
rtt min/avg/max/mdev = 53.581/55.834/88.960/5.110 ms

AT&T WorldNet, Colorado (my office).

Posted by: Erbo at June 11, 2007 11:29 AM (HJOoz)

22 oops...I must have been pulling the info off my other window just as you posted the "thanks everyone!" message...

Posted by: Erbo at June 11, 2007 11:30 AM (HJOoz)

23 The internet is full of weirdness and irony. I've had pingplotter running all morning, and it's been getting progressively worse. For the last hour it's been solid 100% packets lost. Which means that the only way I can get from Oregon to Texas to leave comments here is by using Anonymouse.org, a free anonymizing proxy in Germany.

Posted by: Steven Den Beste at June 11, 2007 12:06 PM (aTZaE)

24 Ping statistics for 75.126.89.164:
    Packets: Sent = 100, Received = 85, Lost = 15 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 48ms, Average = 46ms

Verizon FiOS, PA

(Doesn't look like it's getting any better ...)

Posted by: AJD at June 11, 2007 12:17 PM (stNWd)

25 And I don't have to go through the proxy anymore. Yaay!!!

Posted by: Steven Den Beste at June 11, 2007 02:00 PM (+rSRq)

26 I can't believe this; it's gotten worse again! Come on, you guys! Get your act together! I'm back to 41 out of 100 lost pings.

Posted by: Steven Den Beste at June 11, 2007 08:43 PM (aTZaE)

27 It's gotten gradually better in the last two hours but it's still not ideal. I'm going to leave pingplotter running overnight.

Posted by: Steven Den Beste at June 11, 2007 10:32 PM (+rSRq)

Hide Comments | Add Comment