bgpreport

Network · data from 2026-11-12

AS202813 Liberatel Comunicaciones

Registry name: ASLIBER LIBERATEL COMUNICACIONES, S.L., ES · PeeringDB

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

Announced routes

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

5.59.60.0/23 Valid Nonecovered by 5.59.60.0/22 673 100% 66
5.59.61.0/24 Valid Nonecovered by 5.59.60.0/22 673 100% 66
5.59.62.0/24 Valid Nonecovered by 5.59.60.0/22 673 100% 66
5.59.64.0/23 Valid Nonecovered by 5.59.64.0/22 673 100% 66
5.59.66.0/24 Valid Nonecovered by 5.59.64.0/22 673 100% 66
5.59.67.0/24 Valid Nonecovered by 5.59.64.0/22 673 100% 66
5.59.172.0/24 Valid RIR databaseRIPE 673 100% 66
5.59.173.0/24 Valid RIR databaseRIPE 673 100% 66
5.154.6.0/24 Valid RIR databaseRIPE 673 100% 66
5.154.69.0/24 Valid RIR databaseRIPE 673 100% 66
5.154.83.0/24 Valid RIR databaseRIPE 673 100% 66
185.14.60.0/24 Valid RIR databaseRIPE 673 100% 66
185.14.61.0/24 Valid RIR databaseRIPE 673 100% 66
185.14.62.0/23 Valid RIR databaseRIPE 673 100% 66
185.153.224.0/24 Valid RIR databaseRIPE 673 100% 66
185.153.225.0/24 Valid RIR databaseRIPE 673 100% 66
185.153.226.0/24 Valid RIR databaseRIPE 673 100% 66
185.153.227.0/24 Valid RIR databaseRIPE 673 100% 66
185.178.16.0/23 Valid RIR databaseRIPE 673 100% 66
185.178.18.0/24 Valid RIR databaseRIPE 673 100% 66
185.178.19.0/24 Valid RIR databaseRIPE 673 100% 66
185.178.136.0/22 Valid RIR databaseRIPE 673 100% 66
185.242.172.0/24 Valid RIR databaseRIPE 673 100% 66
45.88.152.0/24 Valid RIR databaseRIPE 672 100% 66
45.88.153.0/24 Valid RIR databaseRIPE 672 100% 66
45.88.154.0/24 Valid RIR databaseRIPE 672 100% 66
45.88.155.0/24 Valid RIR databaseRIPE 672 100% 66
2a09:74c0::/29 Valid RIR databaseRIPE 633 100% 67
2a0b:fa80::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS202813: AS-NET-LIBERATEL. 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 (AS202813 isn't in the set, or no route object for AS202813 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 objectsAS202813 in itNot covered
AS-NET-LIBERATEL RIPE 1143 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 26 are in fix.csv.

  • Route object: none6
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: none5.59.60.0/23No route object for it. A route object for 5.59.60.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673
Route object: none5.59.61.0/24No route object for it. A route object for 5.59.60.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673
Route object: none5.59.62.0/24No route object for it. A route object for 5.59.60.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673
Route object: none5.59.64.0/23No route object for it. A route object for 5.59.64.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673
Route object: none5.59.66.0/24No route object for it. A route object for 5.59.64.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673
Route object: none5.59.67.0/24No route object for it. A route object for 5.59.64.0/22 with origin AS202813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202813 in the RIR database for the space.673 of 673

Route objects not announced

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

5.59.60.0/22RIPEValid
5.59.64.0/22RIPEValid
45.88.152.0/22RIPEValid
45.88.152.0/23RIPEValid
45.88.154.0/23RIPEValid
185.14.60.0/22RIPEValid
185.14.60.0/23RIPEValid
185.14.62.0/24RIPEValid
185.14.63.0/24RIPEValid
185.153.224.0/22RIPEValid
185.153.224.0/23RIPEValid
185.153.226.0/23RIPEValid
185.178.16.0/22RIPEValid
185.178.16.0/24RIPEValid
185.178.17.0/24RIPEValid
185.178.18.0/23RIPEValid
185.178.136.0/24RIPEValid
185.178.137.0/24RIPEValid
185.178.138.0/24RIPEValid
185.178.139.0/24RIPEValid

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.