bgpreport

Network · data from 2026-11-12

AS16531 Protel i-Next

Registry name: AS16531 - TOPNET SA de CV, MX · PeeringDB

25IPv4 routes 92.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS16531, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16531, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

200.76.126.0/24 No ROA Other IRR onlyRADB 672 100% 67
200.76.125.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.52.130.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.131.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.135.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.138.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.139.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.143.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.96.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.101.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.105.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.106.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.107.0/24 Valid Other IRR onlyRADB 672 100% 67
200.76.109.0/24 Valid Other IRR onlyRADB 672 100% 67
200.52.128.0/24 Valid Other IRR onlyRADB 671 100% 67
200.52.129.0/24 Valid Other IRR onlyRADB 671 100% 67
200.52.132.0/24 Valid Other IRR onlyRADB 671 100% 67
200.52.133.0/24 Valid Other IRR onlyRADB 671 100% 67
200.52.134.0/24 Valid Other IRR onlyRADB 671 100% 67
200.52.136.0/24 Valid Other IRR onlyRADB 671 100% 67
200.76.98.0/24 Valid Other IRR onlyRADB 671 100% 67
200.76.104.0/24 Valid Other IRR onlyRADB 671 100% 67
200.76.108.0/24 Valid Other IRR onlyRADB 671 100% 67
200.76.110.0/24 Valid Other IRR onlyRADB 671 100% 67
200.76.111.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS16531's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 54 are in fix.csv.

  • ROA: none2
  • Route object: RIR25
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: none200.76.126.0/24No ROA covers it. Add a ROA for AS16531, maxLength 24.672 of 673
Route object: RIR200.76.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.76.125.0/24No ROA covers it. Add a ROA for AS16531, maxLength 24.671 of 673
Route object: RIR200.76.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.130.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.135.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.138.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.139.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.143.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.96.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.105.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.106.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.107.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.76.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.52.128.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.129.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.132.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.133.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.134.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.52.136.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.76.98.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.76.104.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.76.108.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.76.110.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.76.111.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS16531 whose prefix no peer sees AS16531 announce. Many are kept on purpose (backup routes, space announced only in some places).

63.175.44.0/23RADBNo ROA
200.52.128.0/20LACNIC, RADBValid
200.52.137.0/24RADBValid
200.52.140.0/24RADBValid
200.52.141.0/24RADBValid
200.52.142.0/24RADBValid
200.76.96.0/19RADBNo ROA
200.76.96.0/20LACNIC, RADBValid
200.76.97.0/24RADBValid
200.76.99.0/24RADBValid
200.76.100.0/24RADBValid
200.76.102.0/24RADBValid
200.76.103.0/24RADBValid
200.76.112.0/20RADBNo ROA
200.76.117.0/24RADBNo ROA
200.76.124.0/24RADBNo ROA
200.76.127.0/24RADBNo ROA
201.159.80.0/24RADBNo ROA
201.161.132.0/22RADBNo ROA
201.161.136.0/21RADBNo ROA
201.161.144.0/20RADBNo ROA
201.161.173.0/24RADBNo ROA
201.161.174.0/24RADBNo ROA
201.161.175.0/24RADBNo ROA
201.161.176.0/21RADBNo ROA
2001:1200::/32RADBNo ROA
2806:339::/32RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.