Softlayer/Network layer partial outage in Asian region?
Seems like Softlayer/Network layer having rouitng glitches in Asia. Their prefix 216.12.192.0/19 is not working in South East. Route goes till Singapore router and times out there. traceroute to hostgator.com (216.12.194.67), 30 hops max, 60 byte packets 1 router.local (192.168.1.1) 1.576 ms 2.025 ms 2.508 ms 2 117.212.40.1 (117.212.40.1) 26.500 ms 29.397 ms 31.717 ms 3 218.248.173.46 (218.248.173.46) 35.014 ms 36.184 ms 38.806 ms 4 115.249.245.198 (115.249.245.198) 50.224 ms 54.037 ms 56.476 ms 5 115.255.252.149 (115.255.252.149) 100.129 ms 101.235 ms 106.338 ms 6 62.216.147.249 (62.216.147.249) 115.066 ms 116.228 ms 118.407 ms 7 ge-1-0-0.0.cjr02.chn001.flagtel.com (62.216.135.226) 121.183 ms 83.215 ms so-7-0-0.0.ejr03.sin001.flagtel.com (62.216.128.73) 116.212 ms 8 so-7-1-0.0.ejr04.sin001.flagtel.com (62.216.128.153) 116.677 ms 118.551 ms 62.216.128.246 (62.216.128.246) 121.665 ms 9 p6453.sgw.equinix.com (202.79.197.19) 162.612 ms 163.006 ms 163.631 ms 10 ae12.bbr01.eq01.sng02.networklayer.com (120.29.215.102) 167.409 ms 169.761 ms 173.955 ms 11 ae6.dar02.sr03.sng01.networklayer.com (50.97.18.203) 177.675 ms 180.009 ms ae5.dar02.sr03.sng01.networklayer.com (50.97.18.199) 171.207 ms 12 po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) 180.555 ms * * 13 * * * 14 * * * I wonder what causes such issues? Clearly issue is within Softlayer's AS 36351. So is it like broken OSPF inside or iBGP? -- Anurag Bhatia anuragbhatia.com Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia>| Google+ <https://plus.google.com/118280168625121532854>
No issues in other parts of the south east. But interestingly I just circled around the globe to reach the destination you mentioned as per the ptr. traceroute to 216.12.194.67 (216.12.194.67), 30 hops max, 60 byte packets 1 124.29.233.141 (124.29.233.141) 0.303 ms 0.413 ms 0.442 ms 2 ge-1-3-0-edge01-khi.cyber.net.pk (202.163.97.234) 0.426 ms 0.455 ms 0.535 ms 3 fe-0-1-0-edge2.khi.pk (61.5.158.252) 0.328 ms 0.413 ms 0.741 ms 4 khi77.pie.net.pk (221.120.205.77) 0.334 ms 0.363 ms 0.748 ms 5 rwp44.pie.net.pk (221.120.251.145) 12.567 ms 12.499 ms 12.534 ms 6 Sw275b-khi77c1.pie.net.pk (202.125.128.133) 0.736 ms 0.878 ms 1.420 ms 7 static-khi-ni01-swa.pie.net.pk (202.125.128.162) 1.725 ms 1.666 ms 1.704 ms 8 khi77.pie.net.pk (202.125.134.162) 140.570 ms 140.535 ms 140.479 ms 9 bbr01.eq01.ams01.networklayer.com (195.69.146.82) 137.135 ms 137.284 ms 136.565 ms 10 ae7.bbr02.eq01.ams02.networklayer.com (50.97.18.213) 142.482 ms 142.436 ms 142.362 ms 11 ae0.bbr02.tg01.lon01.networklayer.com (50.97.18.210) 136.787 ms 137.905 ms 137.632 ms 12 ae7.bbr01.tg01.lon01.networklayer.com (50.97.18.206) 138.000 ms 137.772 ms 137.729 ms 13 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 238.551 ms 244.034 ms 241.251 ms 14 ae1.bbr01.eq01.chi01.networklayer.com (173.192.18.132) 262.464 ms 261.560 ms 262.212 ms 15 ae7.bbr02.eq01.chi01.networklayer.com (173.192.18.171) 259.721 ms 261.217 ms 261.276 ms 16 ae1.bbr02.cs01.den01.networklayer.com (173.192.18.131) 286.070 ms 284.922 ms 284.897 ms 17 ae1.bbr01.eq01.sjc02.networklayer.com (173.192.18.148) 312.360 ms 313.124 ms 312.879 ms 18 ae7.bbr02.eq01.sjc02.networklayer.com (173.192.18.165) 311.651 ms 316.019 ms 316.875 ms 19 ae0.bbr01.eq01.tok01.networklayer.com (50.97.18.161) 409.615 ms 413.119 ms 413.175 ms 20 ae1.bbr01.eq01.sng02.networklayer.com (50.97.18.165) 273.512 ms 272.463 ms 273.586 ms 21 ae5.dar02.sr03.sng01.networklayer.com (50.97.18.199) 274.449 ms 274.857 ms ae5.dar01.sr03.sng01.networklayer.com (50.97.18.197) 274.261 ms 22 po1.fcr01.sr03.sng01.networklayer.com (174.133.118.131) 271.876 ms po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) 272.995 ms * 23 216.12.194.67-static.reverse.softlayer.com (216.12.194.67) 275.354 ms 314.130 ms 314.024 ms [kindly excuse for the noise] Regards, Aftab A. Siddiqui On Thu, Sep 13, 2012 at 1:39 PM, Anurag Bhatia <me@anuragbhatia.com> wrote:
Seems like Softlayer/Network layer having rouitng glitches in Asia.
Their prefix 216.12.192.0/19 is not working in South East. Route goes till Singapore router and times out there.
traceroute to hostgator.com (216.12.194.67), 30 hops max, 60 byte packets 1 router.local (192.168.1.1) 1.576 ms 2.025 ms 2.508 ms 2 117.212.40.1 (117.212.40.1) 26.500 ms 29.397 ms 31.717 ms 3 218.248.173.46 (218.248.173.46) 35.014 ms 36.184 ms 38.806 ms 4 115.249.245.198 (115.249.245.198) 50.224 ms 54.037 ms 56.476 ms 5 115.255.252.149 (115.255.252.149) 100.129 ms 101.235 ms 106.338 ms 6 62.216.147.249 (62.216.147.249) 115.066 ms 116.228 ms 118.407 ms 7 ge-1-0-0.0.cjr02.chn001.flagtel.com (62.216.135.226) 121.183 ms 83.215 ms so-7-0-0.0.ejr03.sin001.flagtel.com (62.216.128.73) 116.212 ms 8 so-7-1-0.0.ejr04.sin001.flagtel.com (62.216.128.153) 116.677 ms 118.551 ms 62.216.128.246 (62.216.128.246) 121.665 ms 9 p6453.sgw.equinix.com (202.79.197.19) 162.612 ms 163.006 ms 163.631 ms 10 ae12.bbr01.eq01.sng02.networklayer.com (120.29.215.102) 167.409 ms 169.761 ms 173.955 ms 11 ae6.dar02.sr03.sng01.networklayer.com (50.97.18.203) 177.675 ms 180.009 ms ae5.dar02.sr03.sng01.networklayer.com (50.97.18.199) 171.207 ms 12 po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) 180.555 ms * * 13 * * * 14 * * *
I wonder what causes such issues? Clearly issue is within Softlayer's AS 36351. So is it like broken OSPF inside or iBGP?
--
participants (2)
-
Aftab Siddiqui
-
Anurag Bhatia