bgpreport

Network · data from 2026-11-12

AS268552 NETSBRASIL

Registry name: AS268552 - NETSBRASIL LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268552, 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.163.104.0/23 Valid Nonecovered by 45.163.104.0/22 672 100% 67
45.163.104.0/24 Valid Nonecovered by 45.163.104.0/22 670 100% 67
45.163.105.0/24 Valid Nonecovered by 45.163.104.0/22 670 100% 67
45.163.106.0/24 Valid Nonecovered by 45.163.104.0/22 669 99% 67
45.163.107.0/24 Valid Nonecovered by 45.163.104.0/22 669 99% 67
2804:52f4::/34 Valid Nonecovered by 2804:52f4::/32 631 99% 67
45.163.104.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
2804:52f4::/32 Valid Other IRR onlyALTDB, RADB 634 100% 69

AS-SET

AS268552'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 8 are in fix.csv.

  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.163.104.0/23No route object for it. A route object for 45.163.104.0/22 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.672 of 673
Route object: none45.163.104.0/24No route object for it. A route object for 45.163.104.0/22 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.670 of 673
Route object: none45.163.105.0/24No route object for it. A route object for 45.163.104.0/22 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.670 of 673
Route object: none45.163.106.0/24No route object for it. A route object for 45.163.104.0/22 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.669 of 673
Route object: none45.163.107.0/24No route object for it. A route object for 45.163.104.0/22 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.669 of 673
Route object: none2804:52f4::/34No route object for it. A route object for 2804:52f4::/32 with origin AS268552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268552 in the RIR database for the space.631 of 636
Route object: RIR45.163.104.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:52f4::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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