bgpreport

Network · data from 2026-11-12

AS273586 AS273586 - FLAVIO FERNANDO COSTA

Registry name: AS273586 - FLAVIO FERNANDO COSTA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273586, 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.
204.157.145.0/24 No ROA Nonecovered by 204.157.144.0/23 671 100% 67
204.157.144.0/24 No ROA Nonecovered by 204.157.144.0/23 670 100% 67
2804:892c::/33 No ROA Nonecovered by 2804:892c::/32 636 100% 67
2804:892c:8000::/33 No ROA Nonecovered by 2804:892c::/32 636 100% 67
204.157.144.0/23 No ROA Other IRR onlyRADB 671 100% 66
2804:892c::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none204.157.145.0/24No ROA covers it. Add a ROA for AS273586, maxLength 24.671 of 673
Route object: none204.157.145.0/24No route object for it. A route object for 204.157.144.0/23 with origin AS273586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273586 in the RIR database for the space.671 of 673
ROA: none204.157.144.0/24No ROA covers it. Add a ROA for AS273586, maxLength 24.670 of 673
Route object: none204.157.144.0/24No route object for it. A route object for 204.157.144.0/23 with origin AS273586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273586 in the RIR database for the space.670 of 673
ROA: none2804:892c::/33No ROA covers it. Add a ROA for AS273586, maxLength 33.636 of 636
Route object: none2804:892c::/33No route object for it. A route object for 2804:892c::/32 with origin AS273586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273586 in the RIR database for the space.636 of 636
ROA: none2804:892c:8000::/33No ROA covers it. Add a ROA for AS273586, maxLength 33.636 of 636
Route object: none2804:892c:8000::/33No route object for it. A route object for 2804:892c::/32 with origin AS273586 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273586 in the RIR database for the space.636 of 636
ROA: none204.157.144.0/23No ROA covers it. Add a ROA for AS273586, maxLength 23.671 of 673
Route object: RIR204.157.144.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:892c::/32No ROA covers it. Add a ROA for AS273586, maxLength 32.636 of 636
Route object: RIR2804:892c::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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