pathping screen scrape

[HTM~ZenEye]

Tracing route to 72.29.117.219 over a maximum of 30 hops

0 blue2 [192.168.13.38]
1 192.168.13.37
2 bdl1.eas-ubr10.atw-eas.pa.cable.rcn.net [10.19.152.1]
3 vl4.aggr1.phdl.pa.rcn.net [208.59.252.1]
4 ge4-0.core2.phdl.pa.rcn.net [207.172.15.51]
5 pos6-0.core3.nyw.ny.rcn.net [207.172.19.11]
6 ge3-0.border3.nyw.ny.rcn.net [207.172.15.68]
7 NYCL-PEER-03.twtelecom.net [198.32.118.36]
8 hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
9 64-129-174-182.static.twtelecom.net [64.129.174.182]
10 ge-1-2.core2.colo4dallas.net [206.123.64.30]
11 206.123.64.54
12 72.29.117.219

Computing statistics for 300 seconds...
Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 blue2 [192.168.13.38]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.13.37
0/ 100 = 0% |

2 7ms 0/ 100 = 0% 0/ 100 = 0% bdl1.eas-ubr10.atw-eas.pa.cable.rcn.net [10.19.152.1]
1/ 100 = 1% |

3 16ms 1/ 100 = 1% 0/ 100 = 0% vl4.aggr1.phdl.pa.rcn.net [208.59.252.1]
0/ 100 = 0% |

4 12ms 6/ 100 = 6% 5/ 100 = 5% ge4-0.core2.phdl.pa.rcn.net [207.172.15.51]
0/ 100 = 0% |

5 14ms 6/ 100 = 6% 5/ 100 = 5% pos6-0.core3.nyw.ny.rcn.net [207.172.19.11]
0/ 100 = 0% |

6 14ms 6/ 100 = 6% 5/ 100 = 5% ge3-0.border3.nyw.ny.rcn.net [207.172.15.68]
0/ 100 = 0% |

7 16ms 1/ 100 = 1% 0/ 100 = 0% NYCL-PEER-03.twtelecom.net [198.32.118.36]
0/ 100 = 0% |

8 --- 100/ 100 =100% 99/ 100 = 99% hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
0/ 100 = 0% |

9 61ms 4/ 100 = 4% 3/ 100 = 3% 64-129-174-182.static.twtelecom.net [64.129.174.182]
0/ 100 = 0% |

10 56ms 1/ 100 = 1% 0/ 100 = 0% ge-1-2.core2.colo4dallas.net [206.123.64.30]
2/ 100 = 2% |

11 59ms 3/ 100 = 3% 0/ 100 = 0% 206.123.64.54
5/ 100 = 5% |

12 55ms 8/ 100 = 8% 0/ 100 = 0% 72.29.117.219

Trace complete.

you can see where the problem is, i pinged that router and it responded fine. the problem is very intermittent, sometimes small pl sometimes very large, seems like that router might be going down. i'll just have to wait untill i get rerouted by bgp/ospf... <sigh>

p.s. heres my new excuse keybind: "I don't suck, its the PL dammit!"

[HTM|Massive~NUTZ]

yeah, i saw that pl too...

Ping statistics for 64.129.234.20:
Packets: Sent = 1556, Received = 1199, Lost = 357 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 254ms, Average = 101ms

Can't you open a ticket with your ISP to have them engage Time Warner? RCN peers directly with them.


One interesting thing to note is that i got destination unreachable last night. So at least you were getting a message back from the router. It may be slammed and can't respond to the ping packets.

This morning though, i'm getting request timed out for each dropped packet. It doesn't even bother to respond or there some sore of route flapping or something going on...like it's sending the response through a different path that never makes it back...who knows. Open a trouble ticket.

[HTM~ZenEye]

yeah if it continues i will open a support ticket like you said. "normally" this kind of thing takes care of itself, and i played this morning and didn't see any pl, however i was the only one connected to the server. Hopefully you and I aren't the only ones who noticed and time warner will fix the prob or bring up a redundant route to balance the load some. wee shall see...

[HTM~ZenEye]

Gaddamnmuthafunkingshiz

Just fired an email to RCN's NOC, hopefully i will get a response. Played on sanc tonite and got PL with server only half full.

goto: thread title