Customer complaining of slow response

[graham]

Anyone see anything wrong with this, please?

Tracing route to xxxxxxx.xxx [64.191.xx.xxx] over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.123.254
2 20 ms 12 ms 13 ms medubr01-cb1.kabsi.at [10.131.0.1]
3 12 ms 12 ms 13 ms gig1-13.core02.kabsi.at [195.202.135.97]
4 24 ms 13 ms 13 ms VIX-gw20.VIE.AT.net.DTAG.DE [62.156.138.125]
5 47 ms 46 ms 49 ms ams-e4.AMS.NL.net.DTAG.DE [62.154.15.2]
6 118 ms 111 ms 107 ms core01.ams03.atlas.cogentco.com [195.69.144.124]
7 137 ms 132 ms 129 ms p5-0.core01.lon01.atlas.cogentco.com [130.117.1.58]
8 126 ms 129 ms 129 ms p6-0.core01.jfk01.atlas.cogentco.com [154.54.1.57]
9 129 ms 138 ms 135 ms p15-0.core02.jfk01.atlas.cogentco.com [66.28.4.166]
10 160 ms 127 ms 128 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.169]
11 137 ms 138 ms 130 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2]
12 135 ms 135 ms 140 ms g7.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.138]
13 129 ms 130 ms 135 ms BurstNet.demarc.cogentco.com [38.112.11.122]
14 137 ms 136 ms 160 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
15 138 ms 137 ms 144 ms xxxxxxx.xxx [64.191.xx.xxx]

Trace complete.

And here is the ping:
Pinging xxxxxxx.xxx [64.191.xx.xxx] with 32 bytes of data:

Reply from 64.191.xx.xxx: bytes=32 time=139ms TTL=53
Reply from 64.191.xx.xxx: bytes=32 time=138ms TTL=53
Reply from 64.191.xx.xxx: bytes=32 time=137ms TTL=53
Reply from 64.191.xx.xxx: bytes=32 time=138ms TTL=53

[creeper]

Looks like it was a cognant issue.. also looks like they to the router down!!

route-views.on>traceroute 66.197.191.45

Type escape sequence to abort.
Tracing the route to ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45)

1 toroonxngr00.bb.telus.com (154.11.63.85) [AS 852] 0 msec 0 msec 0 msec
2 Cogent.toroonxngr00.bb.telus.com (154.11.3.154) [AS 852] 0 msec 0 msec 0 mse
c
3 p6-0.core01.bos01.atlas.cogentco.com (66.28.4.217) [AS 174] 28 msec 24 msec
28 msec
4 p5-0.core01.jfk02.atlas.cogentco.com (66.28.4.118) [AS 174] 28 msec 24 msec
28 msec
5 p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) [AS 174] 28 msec 28 msec
24 msec
6 p14-0.core01.phl01.atlas.cogentco.com (66.28.4.2) [AS 174] 28 msec 28 msec 2
8 msec
7 g7.ba21.b003003-1.phl01.atlas.cogentco.com (38.112.34.138) [AS 174] 32 msec
32 msec 28 msec
8 BurstNet.demarc.cogentco.com (38.112.11.122) [AS 174] 28 msec 28 msec 28 mse
c
9 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) [AS 21788] 60 msec * 140
msec


the router you saw spikes on isn't responding at all right now~!~


route-views.on>traceroute 195.69.144.124

Type escape sequence to abort.
Tracing the route to core01.ams03.atlas.cogentco.com (195.69.144.124)

1 * * *
2 * *
route-views.on>ping 195.69.144.124 <----where your issues started

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 195.69.144.124, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
route-views.on>ping 130.117.1.58 <--------next hop

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 130.117.1.58, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/103/132 ms
route-views.on>

[Troy [ASAPweb]]

http://forums.burst.net/showthread.php?s=&postid=18228#post18228

Already started a thread on this

[creeper]

Originally posted by osfdeath
http://forums.burst.net/showthread.php?s=&postid=18228#post18228

Already started a thread on this

yea saw that.. maybe "cog" is finally taking a look at the router!!

[BurstCEO]

<< route-views.on>traceroute 66.197.191.45 >>

Don't ping the router itself for testing purposes. It's not acurate. You need to ping thru the router to something on the other side. Routers themselves consistantly will show inconsistant/odd results.

SMA
PRES/CEO
BURSTNET

[creeper]

CEO,

I agree that that is possible for routers to show inconsistant/odd results depending on the router and how it is configured!! If you use a CUDA it will always show inconsitant results on a ping.

I was basing my response on the fact that everyother "cog" router is responding fine!!

Thanks