Network · data from 2026-11-12
AS213200 FZink Ferdinand Zink trading as Tube-Hosting
Registry name: FZink Ferdinand Zink trading as Tube-Hosting, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213200, 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.
| 217.144.154.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 31.6.50.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 31.56.120.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 31.57.97.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 82.22.62.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 143.14.44.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 195.24.236.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS213200 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 217.144.154.0/24 | ROAs covering it name AS834, AS8851, AS19905, not AS213200. If AS213200 should announce it, add a ROA for AS213200. |
| Route object: none | 217.144.154.0/24 | Route objects for it name AS834. Add a route object with origin AS213200 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213200 whose prefix no peer sees AS213200 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.176.202.0/24 | RADB, RIPE | Valid |
| 2a07:4b40::/29 | RIPE | Valid |
| 2a13:9500:12d::/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.