bgpreport

Network · data from 2026-11-12

AS513 CERN

Registry name: CERN CERN - European Organization for Nuclear Research, CH · PeeringDB

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

Announced routes

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

188.184.0.0/17 Invalid: maxLength Nonecovered by 188.184.0.0/16 1 0%low visibility 1
188.184.128.0/17 Invalid: maxLength Nonecovered by 188.184.0.0/16 1 0%low visibility 1
188.185.0.0/17 Invalid: maxLength Nonecovered by 188.185.0.0/16 1 0%low visibility 1
188.185.128.0/18 Invalid: maxLength Nonecovered by 188.185.0.0/16 1 0%low visibility 1
188.185.192.0/18 Invalid: maxLength Nonecovered by 188.185.0.0/16 1 0%low visibility 1
2001:1458:100::/44 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1458:200::/44 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1458:300::/44 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1458:901::/48 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1458:d00::/44 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1458:e000::/40 Invalid: maxLength Nonecovered by 2001:1458::/32 1 0%low visibility 1
2001:1459:100::/44 Invalid: maxLength Nonecovered by 2001:1459::/32 1 0%low visibility 1
2001:1459:200::/44 Invalid: maxLength Nonecovered by 2001:1459::/32 1 0%low visibility 1
2001:1459:300::/44 Invalid: maxLength Nonecovered by 2001:1459::/32 1 0%low visibility 1
128.141.0.0/16 Valid RIR databaseRIPE 669 99% 67
128.142.0.0/16 Valid RIR databaseRIPE 669 99% 67
137.138.0.0/16 Valid RIR databaseRIPE 669 99% 67
192.65.196.0/23 Valid RIR databaseRIPE 669 99% 67
192.91.240.0/22 Valid RIR databaseRIPE 669 99% 67
194.12.128.0/18 Valid RIR databaseRIPE 669 99% 67
185.249.56.0/22 Valid RIR databaseRIPE 668 99% 67
188.184.0.0/16 Valid RIR databaseRIPE 668 99% 67
188.185.0.0/16 Valid RIR databaseRIPE 668 99% 67
192.16.155.0/24 Valid RIR databaseRIPE 668 99% 67
192.16.156.0/22 Valid RIR databaseRIPE 668 99% 67
192.16.160.0/22 Valid RIR databaseRIPE 668 99% 67
192.16.164.0/23 Valid RIR databaseRIPE 668 99% 67
192.16.166.0/24 Valid RIR databaseRIPE 668 99% 67
192.65.183.0/24 Valid RIR databaseRIPE 668 99% 67
192.65.184.0/21 Valid RIR databaseRIPE 668 99% 67
192.65.192.0/22 Valid RIR databaseRIPE 668 99% 67
192.91.236.0/22 Valid RIR databaseRIPE 668 99% 67
192.91.244.0/23 Valid RIR databaseRIPE 668 99% 67
192.91.246.0/24 Valid RIR databaseRIPE 668 99% 67
2001:1458::/32 Valid RIR databaseRIPE 631 99% 68
2001:1459::/32 Valid RIR databaseRIPE 631 99% 68

AS-SET

PeeringDB's irr_as_set for AS513: RIPE::AS-CERNEXT. 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 (AS513 isn't in the set, or no route object for AS513 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 objectsAS513 in itNot covered
RIPE::AS-CERNEXT RIPE 915,388 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 31 are in fix.csv.

  • ROA: maxLength14
  • Route object: none14
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength188.184.0.0/17ROA 188.184.0.0/16 AS513 has maxLength 16; the route is a /17. Raise the maxLength, or add a ROA for 188.184.0.0/17.1 of 673
Route object: none188.184.0.0/17No route object for it. A route object for 188.184.0.0/16 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 673
ROA: maxLength188.184.128.0/17ROA 188.184.0.0/16 AS513 has maxLength 16; the route is a /17. Raise the maxLength, or add a ROA for 188.184.128.0/17.1 of 673
Route object: none188.184.128.0/17No route object for it. A route object for 188.184.0.0/16 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 673
ROA: maxLength188.185.0.0/17ROA 188.185.0.0/16 AS513 has maxLength 16; the route is a /17. Raise the maxLength, or add a ROA for 188.185.0.0/17.1 of 673
Route object: none188.185.0.0/17No route object for it. A route object for 188.185.0.0/16 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 673
ROA: maxLength188.185.128.0/18ROA 188.185.0.0/16 AS513 has maxLength 16; the route is a /18. Raise the maxLength, or add a ROA for 188.185.128.0/18.1 of 673
Route object: none188.185.128.0/18No route object for it. A route object for 188.185.0.0/16 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 673
ROA: maxLength188.185.192.0/18ROA 188.185.0.0/16 AS513 has maxLength 16; the route is a /18. Raise the maxLength, or add a ROA for 188.185.192.0/18.1 of 673
Route object: none188.185.192.0/18No route object for it. A route object for 188.185.0.0/16 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 673
ROA: maxLength2001:1458:100::/44ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1458:100::/44.1 of 636
Route object: none2001:1458:100::/44No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1458:200::/44ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1458:200::/44.1 of 636
Route object: none2001:1458:200::/44No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1458:300::/44ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1458:300::/44.1 of 636
Route object: none2001:1458:300::/44No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1458:901::/48ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2001:1458:901::/48.1 of 636
Route object: none2001:1458:901::/48No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1458:d00::/44ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1458:d00::/44.1 of 636
Route object: none2001:1458:d00::/44No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1458:e000::/40ROA 2001:1458::/32 AS513 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2001:1458:e000::/40.1 of 636
Route object: none2001:1458:e000::/40No route object for it. A route object for 2001:1458::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1459:100::/44ROA 2001:1459::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1459:100::/44.1 of 636
Route object: none2001:1459:100::/44No route object for it. A route object for 2001:1459::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1459:200::/44ROA 2001:1459::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1459:200::/44.1 of 636
Route object: none2001:1459:200::/44No route object for it. A route object for 2001:1459::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636
ROA: maxLength2001:1459:300::/44ROA 2001:1459::/32 AS513 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2001:1459:300::/44.1 of 636
Route object: none2001:1459:300::/44No route object for it. A route object for 2001:1459::/32 with origin AS513 covers it (filters allowing more-specifics accept it). Add a route object with origin AS513 in the RIR database for the space.1 of 636

Route objects not announced

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

188.184.0.0/15RIPENo ROA
188.185.32.0/20RIPEInvalid: maxLength
188.185.64.0/18RIPEInvalid: maxLength

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.