bgpreport

Network · data from 2026-11-12

AS267064 AS267064 - Valdine Pereira de Amorim

Registry name: AS267064 - Valdine Pereira de Amorim, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267064, 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:4798::/33 No ROA Nonecovered by 2804:4798::/32 634 100% 67
2804:4798:8000::/33 No ROA Nonecovered by 2804:4798::/32 634 100% 67
45.228.128.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
45.228.128.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.228.130.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.228.128.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.228.129.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.228.130.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.228.131.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:4798::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS267064 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2804:4798::/33No ROA covers it. Add a ROA for AS267064, maxLength 33.634 of 636
Route object: none2804:4798::/33No route object for it. A route object for 2804:4798::/32 with origin AS267064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267064 in the RIR database for the space.634 of 636
ROA: none2804:4798:8000::/33No ROA covers it. Add a ROA for AS267064, maxLength 33.634 of 636
Route object: none2804:4798:8000::/33No route object for it. A route object for 2804:4798::/32 with origin AS267064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267064 in the RIR database for the space.634 of 636
ROA: none45.228.128.0/22No ROA covers it. Add a ROA for AS267064, maxLength 22.671 of 673
Route object: RIR45.228.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.228.128.0/23No ROA covers it. Add a ROA for AS267064, maxLength 23.671 of 673
Route object: RIR45.228.128.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.228.130.0/23No ROA covers it. Add a ROA for AS267064, maxLength 23.671 of 673
Route object: RIR45.228.130.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.228.128.0/24No ROA covers it. Add a ROA for AS267064, maxLength 24.670 of 673
Route object: RIR45.228.128.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.228.129.0/24No ROA covers it. Add a ROA for AS267064, maxLength 24.670 of 673
Route object: RIR45.228.129.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.228.130.0/24No ROA covers it. Add a ROA for AS267064, maxLength 24.670 of 673
Route object: RIR45.228.130.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.228.131.0/24No ROA covers it. Add a ROA for AS267064, maxLength 24.670 of 673
Route object: RIR45.228.131.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:4798::/32No ROA covers it. Add a ROA for AS267064, maxLength 32.634 of 636
Route object: RIR2804:4798::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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