bgpreport

Network · data from 2026-11-12

AS53172 Next Telecomunicações do Brasil LTDA

Registry name: AS53172 - Next Telecomunicacoes do Brasil LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53172, 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.

2804:2980:f700::/40 Valid Nonecovered by 2804:2980:8000::/33 635 100% 68
2804:2980:fe00::/48 Valid Nonecovered by 2804:2980:8000::/33 112 18% 41
143.137.8.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
143.137.8.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
186.225.64.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
186.225.64.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.66.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.66.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
186.225.68.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.70.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.72.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.74.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.76.0/23 Valid Other IRR onlyTC 672 100% 66
186.225.77.0/24 Valid Other IRR onlyTC 672 100% 66
186.225.78.0/23 Valid Other IRR onlyTC 672 100% 66
143.137.10.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
186.225.79.0/24 Valid Other IRR onlyTC 671 100% 67
2804:2980::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:2980::/33 Valid Other IRR onlyRADB, TC 633 100% 67
2804:2980:8000::/33 Valid Other IRR onlyRADB, TC 633 100% 67
2804:2980:f600::/40 Valid Other IRR onlyRADB 633 100% 67
143.137.8.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
143.137.9.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
143.137.11.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
186.225.64.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.65.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.67.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.68.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.69.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.71.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
186.225.72.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
186.225.73.0/24 Valid Other IRR onlyRADB, TC 147 22% 46
186.225.74.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.75.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.76.0/24 Valid Other IRR onlyTC 147 22% 46
186.225.78.0/24 Valid Other IRR onlyTC 147 22% 46

AS-SET

AS53172'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 44 are in fix.csv.

  • Route object: none2
  • Route object: RIR34
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2804:2980:f700::/40No route object for it. A route object for 2804:2980:8000::/33 with origin AS53172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53172 in the RIR database for the space.635 of 636
Route object: none2804:2980:fe00::/48No route object for it. A route object for 2804:2980:8000::/33 with origin AS53172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53172 in the RIR database for the space.112 of 636
Route object: RIR143.137.8.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.137.8.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.64.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.64.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.66.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.66.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.68.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.70.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.72.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.74.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.76.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.77.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.225.78.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.137.10.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.225.79.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2980::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2980::/33Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2980:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:2980:f600::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR143.137.8.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR143.137.9.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR143.137.11.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.64.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.65.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.67.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.68.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.69.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.71.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.72.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.73.0/24Route object only in RADB, TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.74.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.75.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.76.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673
Route object: RIR186.225.78.0/24Route object only in TC. Add it in the RIR database for the space.147 of 673

Route objects not announced

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

143.137.10.0/24TCValid
186.225.64.0/21TCValid
186.225.64.0/22RADBValid
186.225.68.0/22RADBValid
186.225.70.0/24TCValid
186.225.72.0/21TCValid
186.225.72.0/22RADBValid
186.225.76.0/22RADBValid

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.