bgpreport

Network · data from 2026-11-12

AS265848 FIBERMAX

Registry name: AS265848 - FIBERMAX S.A., AR · PeeringDB

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

Announced routes

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

45.224.104.0/24 Valid Nonecovered by 45.224.104.0/22 4 1%low visibility 3
45.224.105.0/24 Valid Nonecovered by 45.224.104.0/22 4 1%low visibility 3
45.224.106.0/24 Valid Nonecovered by 45.224.104.0/22 4 1%low visibility 3
45.224.107.0/24 Valid Nonecovered by 45.224.104.0/22 4 1%low visibility 3
45.224.104.0/22 Valid RIR databaseLACNIC 671 100% 66
2803:4a20::/32 Valid RIR databaseLACNIC, RADB 628 99% 67

AS-SET

PeeringDB's irr_as_set for AS265848: AS265848:AS-FIBERMAX. 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 (AS265848 isn't in the set, or no route object for AS265848 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 objectsAS265848 in itNot covered
AS265848:AS-FIBERMAX LACNIC 11139,079 No 6

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

  • Route object: none4
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none45.224.104.0/24No route object for it. A route object for 45.224.104.0/22 with origin AS265848 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265848 in the RIR database for the space.4 of 673
Route object: none45.224.105.0/24No route object for it. A route object for 45.224.104.0/22 with origin AS265848 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265848 in the RIR database for the space.4 of 673
Route object: none45.224.106.0/24No route object for it. A route object for 45.224.104.0/22 with origin AS265848 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265848 in the RIR database for the space.4 of 673
Route object: none45.224.107.0/24No route object for it. A route object for 45.224.104.0/22 with origin AS265848 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265848 in the RIR database for the space.4 of 673
AS-SET: own ASNAS265848:AS-FIBERMAXAS265848 isn't in AS265848:AS-FIBERMAX (LACNIC) once expanded. Add AS265848 to it.

Route objects not announced

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