bgpreport

Network · data from 2026-11-12

AS264280 Eagle Redes

Registry name: AS264280 - Eagle Redes de Telecomunicacoes Ltda, BR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS264280, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264280, 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:256c:100::/40 Valid Nonecovered by 2804:256c::/32 359 56% 65
2804:256c:200::/40 Valid Nonecovered by 2804:256c::/32 359 56% 65
138.121.44.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
138.255.136.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:256c::/32 Valid Other IRR onlyRADB, TC 635 100% 67
138.121.44.0/24 Valid Other IRR onlyTC 226 34% 58
138.121.45.0/24 Valid Other IRR onlyTC 226 34% 58
138.121.46.0/24 Valid Other IRR onlyTC 226 34% 58
138.255.137.0/24 Valid Other IRR onlyTC 226 34% 58
138.255.136.0/24 Valid Other IRR onlyTC 225 33% 58
138.255.138.0/24 Valid Other IRR onlyTC 225 33% 58
138.255.139.0/24 Valid Other IRR onlyTC 225 33% 58
138.121.44.0/23 Valid Other IRR onlyTC 139 21% 45
138.121.46.0/23 Valid Other IRR onlyTC 139 21% 45
138.121.47.0/24 Valid Other IRR onlyTC 139 21% 45
138.255.136.0/23 Valid Other IRR onlyTC 139 21% 45
138.255.138.0/23 Valid Other IRR onlyTC 139 21% 45

AS-SET

PeeringDB's irr_as_set for AS264280: AS264280:AS-EAGLE. 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 (AS264280 isn't in the set, or no route object for AS264280 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 objectsAS264280 in itNot covered
AS264280:AS-EAGLE TC 1315 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 17 are in fix.csv.

  • Route object: none2
  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: none2804:256c:100::/40No route object for it. A route object for 2804:256c::/32 with origin AS264280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264280 in the RIR database for the space.359 of 636
Route object: none2804:256c:200::/40No route object for it. A route object for 2804:256c::/32 with origin AS264280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264280 in the RIR database for the space.359 of 636
Route object: RIR138.121.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.255.136.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:256c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR138.121.44.0/24Route object only in TC. Add it in the RIR database for the space.226 of 673
Route object: RIR138.121.45.0/24Route object only in TC. Add it in the RIR database for the space.226 of 673
Route object: RIR138.121.46.0/24Route object only in TC. Add it in the RIR database for the space.226 of 673
Route object: RIR138.255.137.0/24Route object only in TC. Add it in the RIR database for the space.226 of 673
Route object: RIR138.255.136.0/24Route object only in TC. Add it in the RIR database for the space.225 of 673
Route object: RIR138.255.138.0/24Route object only in TC. Add it in the RIR database for the space.225 of 673
Route object: RIR138.255.139.0/24Route object only in TC. Add it in the RIR database for the space.225 of 673
Route object: RIR138.121.44.0/23Route object only in TC. Add it in the RIR database for the space.139 of 673
Route object: RIR138.121.46.0/23Route object only in TC. Add it in the RIR database for the space.139 of 673
Route object: RIR138.121.47.0/24Route object only in TC. Add it in the RIR database for the space.139 of 673
Route object: RIR138.255.136.0/23Route object only in TC. Add it in the RIR database for the space.139 of 673
Route object: RIR138.255.138.0/23Route object only in TC. Add it in the RIR database for the space.139 of 673

Route objects not announced

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