Network · data from 2026-11-12
AS213736 UK-ASN Zantan GmbH
Registry name: UK-ASN Zantan GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213736, 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.
| 2a14:cc00:e001::/48 | Valid | None | 633 100% |
| 154.85.67.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 154.85.71.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.200.108.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.200.109.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 82.27.184.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.27.185.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.27.186.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.27.187.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.242.245.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.242.249.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.242.250.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.34.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.37.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.43.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.44.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.50.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.52.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.243.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 151.243.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 154.92.28.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.92.31.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.251.70.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 151.242.247.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 151.242.246.0/24 | Valid | RIR databaseRADB, RIPE | 11 2%low visibility |
AS-SET
AS213736 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 9 are in fix.csv.
- Route object: none1
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a14:cc00:e001::/48 | No route object for it. Add a route object with origin AS213736 in the RIR database for the space. |
| Route object: RIR | 154.85.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.85.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.200.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.200.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213736 whose prefix no peer sees AS213736 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 151.242.248.0/24 | RADB, RIPE | Valid |
| 151.243.53.0/24 | RIPE | Valid |
| 151.243.80.0/24 | RIPE | Valid |
| 151.243.81.0/24 | 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.