bgpreport

Network · data from 2026-11-12

AS268439 AS268439 - Claudenir dos Santos ME

Registry name: AS268439 - Claudenir dos Santos ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268439, 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:513c::/33 Valid Nonecovered by 2804:513c::/32 636 100% 67
2804:513c:a100::/40 Valid Nonecovered by 2804:513c::/32 635 100% 67
2804:513c:a010::/44 Valid Nonecovered by 2804:513c::/32 634 100% 67
45.161.12.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.161.12.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
45.161.14.0/23 Valid Other IRR onlyTC 670 100% 67
2804:513c::/32 Valid Other IRR onlyRADB, TC 636 100% 67
45.161.12.0/24 Valid Other IRR onlyRADB, TC 135 20% 45
45.161.13.0/24 Valid Other IRR onlyRADB, TC 134 20% 45
45.161.14.0/24 Valid Other IRR onlyTC 134 20% 45
45.161.15.0/24 Valid Other IRR onlyTC 134 20% 45

AS-SET

AS268439 isn't in PeeringDB, where networks name their 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 11 are in fix.csv.

  • Route object: none3
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:513c::/33No route object for it. A route object for 2804:513c::/32 with origin AS268439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268439 in the RIR database for the space.636 of 636
Route object: none2804:513c:a100::/40No route object for it. A route object for 2804:513c::/32 with origin AS268439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268439 in the RIR database for the space.635 of 636
Route object: none2804:513c:a010::/44No route object for it. A route object for 2804:513c::/32 with origin AS268439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268439 in the RIR database for the space.634 of 636
Route object: RIR45.161.12.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.161.12.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.161.14.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:513c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR45.161.12.0/24Route object only in RADB, TC. Add it in the RIR database for the space.135 of 673
Route object: RIR45.161.13.0/24Route object only in RADB, TC. Add it in the RIR database for the space.134 of 673
Route object: RIR45.161.14.0/24Route object only in TC. Add it in the RIR database for the space.134 of 673
Route object: RIR45.161.15.0/24Route object only in TC. Add it in the RIR database for the space.134 of 673

Route objects not announced

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