bgpreport

Network · data from 2026-11-12

AS267913 IFRANET

Registry name: AS267913 - IFRANET S.A, AR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% 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
1Route objects not announced registered with origin AS267913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267913, 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.179.92.0/23 Valid Nonecovered by 45.179.92.0/22 668 99% 67
45.179.94.0/23 Valid Nonecovered by 45.179.92.0/22 668 99% 67
45.179.92.0/24 Valid Other IRR onlyRADB 668 99% 67
45.179.95.0/24 Valid Other IRR onlyRADB 668 99% 67
45.179.93.0/24 Valid Other IRR onlyRADB 667 99% 67
45.179.92.0/22 Valid RIR databaseLACNIC, RADB 668 99% 67
2803:e60::/32 Valid RIR databaseLACNIC, RADB 628 99% 67

AS-SET

PeeringDB's irr_as_set for AS267913: AS267913:AS-IFRANET. 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 (AS267913 isn't in the set, or no route object for AS267913 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 objectsAS267913 in itNot covered
AS267913:AS-IFRANET LACNIC 31396 No 7

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

  • Route object: none2
  • Route object: RIR3
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none45.179.92.0/23No route object for it. A route object for 45.179.92.0/22 with origin AS267913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267913 in the RIR database for the space.668 of 673
Route object: none45.179.94.0/23No route object for it. A route object for 45.179.92.0/22 with origin AS267913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267913 in the RIR database for the space.668 of 673
Route object: RIR45.179.92.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.179.95.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.179.93.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
AS-SET: own ASNAS267913:AS-IFRANETAS267913 isn't in AS267913:AS-IFRANET (LACNIC) once expanded. Add AS267913 to it.

Route objects not announced

Route objects with origin AS267913 whose prefix no peer sees AS267913 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.179.94.0/24RADBValid

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.