Network · data from 2026-11-12
AS8925 teuto.net Bielefeld
Registry name: TEUTONET-AS teuto.net Netzdienste GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8925, 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.
| 91.221.204.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 2001:67c:56c::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 212.8.192.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.8.200.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 212.8.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 212.15.192.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.15.200.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 212.15.216.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.8.204.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 212.8.206.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.8.207.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2001:ae0::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2001:ae2:207::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS8925's PeeringDB record names no 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 64 are in fix.csv.
- ROA: none2
- Route object: not announced62
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.221.204.0/23 | No ROA covers it. Add a ROA for AS8925, maxLength 23. |
| ROA: none | 2001:67c:56c::/48 | No ROA covers it. Add a ROA for AS8925, maxLength 48. |
Route objects not announced
Route objects with origin AS8925 whose prefix no peer sees AS8925 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.221.204.0/24 | RIPE | No ROA |
| 91.221.205.0/24 | RIPE | No ROA |
| 193.194.137.0/24 | RADB | No ROA |
| 194.77.41.0/24 | RADB | No ROA |
| 212.8.192.0/19 | RIPE | Valid |
| 212.8.192.0/24 | RIPE | Valid |
| 212.8.193.0/24 | RIPE | Valid |
| 212.8.194.0/24 | RIPE | Valid |
| 212.8.195.0/24 | RIPE | Valid |
| 212.8.196.0/24 | RIPE | Valid |
| 212.8.197.0/24 | RIPE | Valid |
| 212.8.198.0/24 | RIPE | Valid |
| 212.8.199.0/24 | RIPE | Valid |
| 212.8.200.0/24 | RIPE | Valid |
| 212.8.201.0/24 | RIPE | Valid |
| 212.8.202.0/24 | RIPE | Valid |
| 212.8.203.0/24 | RIPE | Valid |
| 212.8.204.0/24 | RIPE | Valid |
| 212.8.205.0/24 | RIPE | Valid |
| 212.8.208.0/24 | RIPE | Valid |
| 212.8.209.0/24 | RIPE | Valid |
| 212.8.210.0/24 | RIPE | Valid |
| 212.8.211.0/24 | RIPE | Valid |
| 212.8.212.0/24 | RIPE | Valid |
| 212.8.213.0/24 | RIPE | Valid |
| 212.8.214.0/24 | RIPE | Valid |
| 212.8.215.0/24 | RIPE | Valid |
| 212.8.216.0/24 | RIPE | Valid |
| 212.8.217.0/24 | RIPE | Valid |
| 212.8.218.0/24 | RIPE | Valid |
| 212.8.219.0/24 | RIPE | Valid |
| 212.8.220.0/22 | RIPE | Valid |
| 212.8.220.0/24 | RIPE | Valid |
| 212.8.221.0/24 | RIPE | Valid |
| 212.8.222.0/24 | RIPE | Valid |
| 212.8.223.0/24 | RIPE | Valid |
| 212.15.192.0/19 | RADB | Valid |
| 212.15.192.0/24 | RIPE | Valid |
| 212.15.193.0/24 | RIPE | Valid |
| 212.15.194.0/24 | RIPE | Valid |
| 212.15.195.0/24 | RIPE | Valid |
| 212.15.196.0/24 | RIPE | Valid |
| 212.15.197.0/24 | RIPE | Valid |
| 212.15.198.0/24 | RIPE | Valid |
| 212.15.199.0/24 | RIPE | Valid |
| 212.15.200.0/24 | RIPE | Valid |
| 212.15.201.0/24 | RIPE | Valid |
| 212.15.202.0/24 | RIPE | Valid |
| 212.15.203.0/24 | RIPE | Valid |
| 212.15.208.0/21 | RIPE | Valid |
| 212.15.216.0/23 | RIPE | Valid |
| 212.15.216.0/24 | RIPE | Valid |
| 212.15.217.0/24 | RIPE | Valid |
| 212.15.218.0/23 | RIPE | Valid |
| 212.15.218.0/24 | RIPE | Valid |
| 212.15.219.0/24 | RIPE | Valid |
| 212.15.220.0/22 | RIPE | Valid |
| 212.15.220.0/24 | RIPE | Valid |
| 212.15.221.0/24 | RIPE | Valid |
| 212.15.222.0/24 | RIPE | Valid |
| 212.15.223.0/24 | RIPE | Valid |
| 217.13.160.0/23 | 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.