nanog mailing list archives
Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO
From: Karsten Elfenbein <karsten.elfenbein () gmail com>
Date: Thu, 18 Sep 2014 23:54:05 +0200
Hi, looks like you mainly use one transit provider (AS812) or your other transit providers correctly filter that prefix. According to https://stat.ripe.net/data/prefix-routing-consistency/data.json?preferred_version=0.7&resource=192.250.24.0%2F22 there is no route object for the 192.250.24.0/22. As a result the AS6453(TATA COMMUNICATIONS (AMERICA) INC) seemed to have started filtering the prefix from AS812. Which reduced the visibility of that prefix. Check the BGplay from the last days: https://stat.ripe.net/192.250.24.0%2F22#tabId=routing so create the correct route object and the prefix should come up over the next day(s) Also get the more specific route objects removed which point to other AS. 192.250.24.0/23 AS702 192.250.24.0/24 AS19294 Karsten 2014-09-18 23:46 GMT+02:00 Karsten Elfenbein <karsten.elfenbein () gmail com>:
Hi, looks like you mainly use one transit provider (AS812) or your other transit providers correctly filter that prefix. According to https://stat.ripe.net/data/prefix-routing-consistency/data.json?preferred_version=0.7&resource=192.250.24.0%2F22 there is no route object for the 192.250.24.0/22. As a result the AS6453(TATA COMMUNICATIONS (AMERICA) INC) seemed to have started filtering the prefix from AS812. Which reduced the visibility of that prefix. Check the BGplay from the last days: https://stat.ripe.net/192.250.24.0%2F22#tabId=routing so create the correct route object and the prefix should come up over the next day(s) Also get the more specific route objects removed which point to other AS. 192.250.24.0/23 AS702 192.250.24.0/24 AS19294 Karsten 2014-09-18 22:42 GMT+02:00 Brock Massel <BMassel () descartes com>:Hi folks, I'm hoping someone can shed some light on the situation. The 192.250.24 addresses have been reachable for several months in the current configuration with no reported issues. Since the 16th we have been hearing reports that destinations in that block are unavailable for some. Several looking glass' report network not in table. Can someone lend a hand? What is the best way to improve this situation? How do we find where the problem is? B
Current thread:
- 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Brock Massel (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Job Snijders (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO sthaug (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Hugo Slabbert (Sep 18)
- RE: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Tony Wicks (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Gary Baribault (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Gary Baribault (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO sthaug (Sep 18)
- Message not available
- RE: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Brock Massel (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Karsten Elfenbein (Sep 18)
- RE: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Brock Massel (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Job Snijders (Sep 18)
- Message not available
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Karsten Elfenbein (Sep 18)
- Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, global crossing, XO Mike Tancsa (Sep 19)