bgpreport

Network · data from 2026-11-12

AS267218 NOVANET Brazil

Registry name: AS267218 - NOVANET LTDA - ME, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS267218, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267218, 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.
45.231.196.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.231.198.0/24 Valid Other IRR onlyRADB 672 100% 66
45.231.196.0/24 Valid Other IRR onlyRADB 671 100% 67
45.231.197.0/24 Valid Other IRR onlyRADB 669 99% 67
45.231.199.0/24 Valid Other IRR onlyRADB 669 99% 67
2804:4a18::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:4a18:aaa8::/46 Valid Other IRR onlyRADB 634 100% 67
2804:4a18:aaac::/46 Valid Other IRR onlyRADB 634 100% 67
2804:4a18:aab8::/46 Valid Other IRR onlyRADB 634 100% 67
2804:4a18:bbbb::/48 Valid Other IRR onlyRADB 634 100% 67
2804:4a18:bbbc::/48 Valid Other IRR onlyRADB 634 100% 67
2804:4a18:bbcb::/48 Valid Other IRR onlyRADB 634 100% 67

AS-SET

AS267218'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 12 are in fix.csv.

  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: RIR45.231.196.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.231.198.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.231.196.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.231.197.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.231.199.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4a18::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:aaa8::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:aaac::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:aab8::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:bbbb::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:bbbc::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4a18:bbcb::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS267218 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.