bgpreport

Network · data from 2026-11-12

AS263450 NBN TELECOM

Registry name: AS263450 - NORTE BRASIL NETWORK TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263450, 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.
168.232.156.0/23 Valid Other IRR onlyTC 673 100% 66
177.91.233.0/24 Valid Other IRR onlyRADB, TC 673 100% 66
177.91.234.0/24 Valid Other IRR onlyRADB, TC 673 100% 66
177.91.235.0/24 Valid Other IRR onlyRADB, TC 673 100% 66
168.232.156.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.156.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.157.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.158.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
168.232.158.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.91.232.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.91.232.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
177.91.234.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
177.91.232.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
2804:1200::/32 Valid Other IRR onlyRADB, TC 636 100% 67
168.232.159.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

AS263450'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 15 are in fix.csv.

  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: RIR168.232.156.0/23Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR177.91.233.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR177.91.234.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR177.91.235.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR168.232.156.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.156.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.157.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.158.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.158.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.232.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.232.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.234.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.232.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:1200::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR168.232.159.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS263450 is announced.

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.