Bad ping times yet again.

[rharmon]

Seems as if the swbell line is being slow again. Sunday morning about 6 am I found it at 1600+ ms. It got better and today its back at it again with:

Request timed out.
Reply from 66.135.32.166: bytes=32 time=659ms TTL=118
Reply from 66.135.32.166: bytes=32 time=703ms TTL=118
Reply from 66.135.32.166: bytes=32 time=684ms TTL=118

Ping statistics for 66.135.32.166:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 659ms, Maximum = 703ms, Average = 682ms

this is not good. Anyone else seeing this? Here is my tracert. Looks like its chugging at hop 8-9

1 45 ms 44 ms 44 ms fe-gw1-pg-2-0.pgtc.net [69.4.198.1]
2 226 ms 57 ms 57 ms sl-gw38-fw-2-4-TS21.sprintlink.net [144.228.133.
173]
3 58 ms 58 ms 57 ms 144.232.11.58
4 59 ms 76 ms 65 ms sl-bb26-fw-15-0.sprintlink.net [144.232.11.90]
5 58 ms 59 ms 57 ms sl-gw39-fw-0-0.sprintlink.net [144.232.11.61]
6 61 ms 69 ms 59 ms sl-swb-58-0.sprintlink.net [144.228.130.186]
7 70 ms 70 ms 68 ms bb1-p4-0.snantx.sbcglobal.net [151.164.240.177]

8 69 ms 69 ms 69 ms ded2-fa0-1-0.snantx.swbell.net [151.164.17.229]

9 639 ms 627 ms 628 ms vip-3027462.cust-rtr.swbell.net [151.164.19.174]

10 649 ms 628 ms 651 ms 10.10.10.3
11 660 ms 653 ms 678 ms colo1.befound.com [66.135.32.166]

[QT]

Not sure if you've came across it yet, but seems as though ServerBeach is looking into it:

Originally posted by knightfoo
It doesn't look like a DoS attack, but we're still looking into it. I'll post something in the Network Status forum once we get more information on what is happening.

-knightfoo

(http://serverbeach.com/forums/showthread.php?s=&threadid=416)

[rharmon]

OH I did miss that, thanks :)