Network · data from 2026-11-12
AS196714 Thüringer Netkom
Registry name: TNETKOM-AS Thueringer Netkom GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS196714, 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.
| 2a02:2250:100:2d::1/128 | Invalid: maxLength | Nonecovered by 2a02:2250::/32 | 2 0%low visibility |
| 2a04:7440::/30 | No ROA | Other origin only | 38 6%low visibility |
| 2a04:8480::/30 | No ROA | RIR databaseRIPE | 633 100% |
| 31.3.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.73.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 171.33.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.38.8.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.137.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 185.38.11.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:2250::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS196714: AS-TNETKOM. 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 (AS196714 isn't in the set, or no route object for AS196714 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 | AS196714 in it | Not covered |
|---|---|---|---|---|---|
| AS-TNETKOM | RIPElists itself further down | 20 | 5 | 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 11 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2a02:2250:100:2d::1/128 | ROA 2a02:2250::/32 AS196714 has maxLength 32; the route is a /128. Raise the maxLength, or add a ROA for 2a02:2250:100:2d::1/128. |
| Route object: none | 2a02:2250:100:2d::1/128 | No route object for it. A route object for 2a02:2250::/32 with origin AS196714 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS196714 in the RIR database for the space. |
| ROA: none | 2a04:7440::/30 | No ROA covers it. Add a ROA for AS196714, maxLength 30. |
| Route object: none | 2a04:7440::/30 | Route objects for it name AS198196. Add a route object with origin AS196714 in the RIR database for the space. |
| ROA: none | 2a04:8480::/30 | No ROA covers it. Add a ROA for AS196714, maxLength 30. |
Route objects not announced
Route objects with origin AS196714 whose prefix no peer sees AS196714 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.3.84.0/23 | RIPE | Valid |
| 31.3.87.0/24 | RIPE | Valid |
| 171.33.184.0/22 | RIPE | Valid |
| 185.38.8.0/23 | RIPE | Valid |
| 185.38.10.0/24 | RIPE | Valid |
| 2a06:e700::/29 | RIPE | No ROA |
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.