Network · data from 2026-11-12
AS20810 Netcom Kassel
Registry name: Netcom-Kassel Netcom Kassel Gesellschaft fuer Telekommunikation mbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20810, 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.
| 2a03:7500::666/128 | Invalid: maxLength | Nonecovered by 2a03:7500::/32 | 4 1%low visibility |
| 80.69.192.0/32 | Invalid: maxLength | Nonecovered by 80.69.192.0/20 | 3 0%low visibility |
| 45.138.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.158.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.69.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 149.249.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.158.180.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.74.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 193.29.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.113.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.102.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:7500::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a03:7500::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS20810: RIPE::AS20810:AS-NETCOM. 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 (AS20810 isn't in the set, or no route object for AS20810 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.
| Name | Database | ASNs | Sets | AS20810 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS20810:AS-NETCOM | RIPE | 2 | 1 | Yes | 2 |
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: maxLength2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2a03:7500::666/128 | ROA 2a03:7500::/29 AS20810 has maxLength 32; ROA 2a03:7500::/32 AS20810 has maxLength 32; the route is a /128. Raise the maxLength, or add a ROA for 2a03:7500::666/128. |
| Route object: none | 2a03:7500::666/128 | No route object for it. A route object for 2a03:7500::/32 with origin AS20810 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS20810 in the RIR database for the space. |
| ROA: maxLength | 80.69.192.0/32 | ROA 80.69.192.0/20 AS20810 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 80.69.192.0/32. |
| Route object: none | 80.69.192.0/32 | No route object for it. A route object for 80.69.192.0/20 with origin AS20810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20810 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20810 whose prefix no peer sees AS20810 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.74.0.0/20 | RIPE | Valid |
| 188.74.16.0/20 | 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.