bgpreport

Network · data from 2026-11-12

AS270923 FENIX BRASIL

Registry name: AS270923 - FENIX BRASIL, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270923, 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.

186.26.68.0/23 Valid Nonecovered by 186.26.68.0/22 672 100% 67
186.26.70.0/23 Valid Nonecovered by 186.26.68.0/22 672 100% 67
186.26.68.0/24 Valid Nonecovered by 186.26.68.0/22 671 100% 66
186.26.69.0/24 Valid Nonecovered by 186.26.68.0/22 671 100% 66
186.26.70.0/24 Valid Nonecovered by 186.26.68.0/22 671 100% 66
186.26.71.0/24 Valid Nonecovered by 186.26.68.0/22 671 100% 66
2804:7390::/33 Valid Nonecovered by 2804:7390::/32 634 100% 67
2804:7390:8000::/33 Valid Nonecovered by 2804:7390::/32 634 100% 67
2804:7390::/34 Valid Nonecovered by 2804:7390::/32 346 54% 65
2804:7390:4000::/34 Valid Nonecovered by 2804:7390::/32 346 54% 65
2804:7390:8000::/34 Valid Nonecovered by 2804:7390::/32 346 54% 65
2804:7390:c000::/34 Valid Nonecovered by 2804:7390::/32 346 54% 65
186.26.68.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:7390::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS270923: AS270923:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS270923 isn't in the set, or no route object for AS270923 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS270923 in itNot covered
AS270923:AS-ALL TC 122 Yes 0

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

  • Route object: none12
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none186.26.68.0/23No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.672 of 673
Route object: none186.26.70.0/23No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.672 of 673
Route object: none186.26.68.0/24No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.671 of 673
Route object: none186.26.69.0/24No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.671 of 673
Route object: none186.26.70.0/24No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.671 of 673
Route object: none186.26.71.0/24No route object for it. A route object for 186.26.68.0/22 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.671 of 673
Route object: none2804:7390::/33No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.634 of 636
Route object: none2804:7390:8000::/33No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.634 of 636
Route object: none2804:7390::/34No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.346 of 636
Route object: none2804:7390:4000::/34No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.346 of 636
Route object: none2804:7390:8000::/34No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.346 of 636
Route object: none2804:7390:c000::/34No route object for it. A route object for 2804:7390::/32 with origin AS270923 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270923 in the RIR database for the space.346 of 636
Route object: RIR186.26.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:7390::/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 AS270923 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.