Network · data from 2026-11-12
AS201011 CORE-BACKBONE Core-Backbone GmbH
Registry name: CORE-BACKBONE Core-Backbone GmbH, DE · not in PeeringDB
33IPv4 routes
69.7% RPKI valid · 97.0% with a route object
17IPv6 routes
94.1% RPKI valid · 94.1% with a route object
0RPKI invalid
0 origin · 0 maxLength
11No ROA
2 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS201011, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS201011, 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.
| 102.222.214.0/24 | No ROA | None | 536 80% |
| 93.159.208.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.209.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.210.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.211.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.212.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.213.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.214.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.159.215.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.103.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a05:e0c0::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 2a01:4a0:12::/48 | Valid | Nonecovered by 2a01:4a0::/29 | 635 100% |
| 2.59.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.56.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 31.7.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 31.7.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.255.0.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.95.0.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.148.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.199.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.142.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.194.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.43.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.104.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.138.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.138.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.138.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:4a0:b::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:e::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:1e::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:30::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:38::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:43::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:45::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:46::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:47::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:48::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:50::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0:56::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:2a00:10::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:4a0::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a01:4a0:17::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS201011 isn't in PeeringDB, where networks name their AS-SET.
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 22 are in fix.csv.
- ROA: none11
- Route object: none2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.222.214.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| Route object: none | 102.222.214.0/24 | No route object for it. Add a route object with origin AS201011 in the RIR database for the space. |
| ROA: none | 93.159.208.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.209.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.210.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.211.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.212.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.213.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.214.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 93.159.215.0/24 | No ROA covers it. Add a ROA for AS201011, maxLength 24. |
| ROA: none | 185.103.8.0/22 | No ROA covers it. Add a ROA for AS201011, maxLength 22. |
| ROA: none | 2a05:e0c0::/29 | No ROA covers it. Add a ROA for AS201011, maxLength 29. |
| Route object: none | 2a01:4a0:12::/48 | No route object for it. A route object for 2a01:4a0::/29 with origin AS201011 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201011 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201011 whose prefix no peer sees AS201011 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.199.128.0/24 | RIPE | Valid |
| 82.199.138.0/24 | RIPE | Valid |
| 82.199.153.0/24 | RIPE | Valid |
| 185.89.36.0/22 | RIPE | Valid |
| 195.138.251.0/24 | RIPE | Invalid: maxLength |
| 195.138.255.0/24 | RIPE | Invalid: maxLength |
| 2a00:1aa0::/29 | RIPE | Invalid: origin |
| 2a01:4a0:42::/48 | RIPE | Valid |
| 2a01:4a0:62::/48 | RIPE | Valid |
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.