thanks everyone for the help, here are the traceroutes. @Frank, thanks for the document, I’m going over it. traceroute to 184.75.220.219 (184.75.220.219), 64 hops max, 52 byte packets 1 [AS0] 172.17.0.1 (172.17.0.1) 1.998 ms 3.296 ms 1.969 ms 2 [AS32580] 67.211.124.89 (67.211.124.89) 7.096 ms 20.431 ms 14.549 ms 3 [AS32580] 204.11.122.11 (204.11.122.11) 31.060 ms 7.706 ms 10.970 ms 4 [AS174] gi2-7.mag02.yyz02.atlas.cogentco.com (38.99.202.185) 6.187 ms 23.907 ms 3.755 ms 5 [AS174] te0-7-0-12.ccr22.yyz02.atlas.cogentco.com (154.54.40.165) 9.520 ms 6.582 ms 6.827 ms 6 [AS174] 38.104.251.246 (38.104.251.246) 9.814 ms 4.868 ms 5.120 ms 7 [AS32489] 184.75.220.219 (184.75.220.219) 4.542 ms 20.715 ms 5.167 ms traceroute to 184.75.220.219 (184.75.220.219), 64 hops max, 52 byte packets 1 [AS0] 172.17.0.1 (172.17.0.1) 11.209 ms 1.253 ms 3.192 ms 2 [AS32580] 67.211.124.89 (67.211.124.89) 6.940 ms 7.744 ms 4.480 ms 3 [AS32580] 204.11.122.11 (204.11.122.11) 2.756 ms 2.883 ms 2.915 ms 4 [AS174] gi2-7.mag02.yyz02.atlas.cogentco.com (38.99.202.185) 30.830 ms 248.287 ms 217.119 ms 5 [AS174] te0-7-0-12.ccr22.yyz02.atlas.cogentco.com (154.54.40.165) 7.014 ms 38.764 ms 10.397 ms 6 [AS174] 38.104.251.246 (38.104.251.246) 38.716 ms * * 7 [AS32489] 184.75.220.219 (184.75.220.219) 4.868 ms 23.644 ms 6.788 ms traceroute to 184.75.220.222 (184.75.220.222), 64 hops max, 52 byte packets 1 [AS0] 172.17.0.1 (172.17.0.1) 10.443 ms 1.233 ms 1.007 ms 2 [AS32580] 67.211.124.89 (67.211.124.89) 5.232 ms 10.124 ms 11.592 ms 3 [AS32580] 204.11.122.11 (204.11.122.11) 13.303 ms 3.953 ms 6.052 ms 4 [AS174] gi2-7.mag02.yyz02.atlas.cogentco.com (38.99.202.185) 3.763 ms 4.178 ms 3.967 ms 5 [AS174] te0-7-0-12.ccr22.yyz02.atlas.cogentco.com (154.54.40.165) 3.958 ms 11.509 ms 4.727 ms 6 * * * 7 [AS32489] 184.75.220.222 (184.75.220.222) 5.754 ms 25.817 ms 7.113 ms
On Sep 24, 2014, at 6:06 PM, Chris Jones <chrisj@aprole.com> wrote:
What you’re seeing could be the result of control-plane policing kicking in - it might be helpful if you could post a traceroute, or give us the actual destination address of your server?
Just because the router IP is showing loss doesn’t mean its not forwarding packets happily…
Chris
On 25 Sep 2014, at 7:39 am, Samer Ziadeh via Outages <outages@outages.org <mailto:outages@outages.org>> wrote:
Does anyone know anything about the IP 38.104.251.246 ? After looking at google, it seems like it's for psi-net.com <http://psi-net.com/>, and it's one of the routers on the way to my server.
Running a ping on that IP, majority of the packets are dropped, and it's causing my site to go down from time to time.
^_^ [~]$ ping 38.104.251.246 PING 38.104.251.246 (38.104.251.246): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 64 bytes from 38.104.251.246 <http://38.104.251.246/>: icmp_seq=3 ttl=56 time=5.468 ms Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 64 bytes from 38.104.251.246 <http://38.104.251.246/>: icmp_seq=9 ttl=56 time=19.022 ms Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 Request timeout for icmp_seq 17 64 bytes from 38.104.251.246 <http://38.104.251.246/>: icmp_seq=18 ttl=56 time=3.957 ms Request timeout for icmp_seq 19 Request timeout for icmp_seq 20 64 bytes from 38.104.251.246 <http://38.104.251.246/>: icmp_seq=21 ttl=56 time=6.522 ms --- 38.104.251.246 ping statistics --- 23 packets transmitted, 4 packets received, 82.6% packet loss round-trip min/avg/max/stddev = 3.957/8.742/19.022/6.005 ms
-- - Samer _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
// Samer