bgpreport

Network · data from 2026-11-12

AS59776 Liberty Global CDN

Registry name: LGI-CDN Liberty Global Europe Holding B.V., NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59776, 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.
185.72.120.0/22 Invalid: origin None 3 0%low visibility 3
185.72.121.0/24 Invalid: origin None 3 0%low visibility 3
2001:678:82c::/48 Invalid: origin None 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS59776: RIPE::AS59776. 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 (AS59776 isn't in the set, or no route object for AS59776 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 objectsAS59776 in itNot covered
RIPE::AS59776 A single AS number, not a set: AS59776 (this network), 0 route objects.

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

  • ROA: origin3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin185.72.120.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59776 should announce it, add a ROA for AS59776.3 of 673
Route object: none185.72.120.0/22No route object for it. Add a route object with origin AS59776 in the RIR database for the space.3 of 673
ROA: origin185.72.121.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59776 should announce it, add a ROA for AS59776.3 of 673
Route object: none185.72.121.0/24No route object for it. Add a route object with origin AS59776 in the RIR database for the space.3 of 673
ROA: origin2001:678:82c::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS59776 should announce it, add a ROA for AS59776.2 of 636
Route object: none2001:678:82c::/48No route object for it. Add a route object with origin AS59776 in the RIR database for the space.2 of 636

Route objects not announced

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