Network · data from 2026-11-12
AS207143 Hosttech GmbH
Registry name: hosttech-AS hosttech GmbH, CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207143, 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.
| 185.101.156.0/22 | Valid | Other origin only | 673 100% |
| 185.101.158.0/24 | Valid | None | 673 100% |
| 185.101.159.0/24 | Valid | None | 673 100% |
| 185.142.212.0/22 | Valid | Other origin only | 673 100% |
| 185.142.212.0/24 | Valid | None | 673 100% |
| 185.142.213.0/24 | Valid | None | 673 100% |
| 185.142.214.0/24 | Valid | None | 673 100% |
| 185.142.215.0/24 | Valid | None | 673 100% |
| 185.178.192.0/22 | Valid | Other origin only | 673 100% |
| 185.178.192.0/24 | Valid | None | 673 100% |
| 185.178.193.0/24 | Valid | None | 673 100% |
| 185.178.194.0/24 | Valid | None | 673 100% |
| 185.178.195.0/24 | Valid | None | 673 100% |
| 193.135.58.0/24 | Valid | Other origin only | 673 100% |
| 95.36.100.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 95.36.102.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.35.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.229.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.229.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.229.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.229.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.135.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.203.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.56.188.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.56.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.56.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.56.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 204.174.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.167.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.167.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.167.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.167.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.254.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.131.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.77.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2001:678:e44::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:3d4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a11:8b81::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a11:8b82::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a11:8b83:1::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS207143'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 16 are in fix.csv.
- Route object: none14
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.101.156.0/22 | Route objects for it name AS9044. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.101.158.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.101.159.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.142.212.0/22 | Route objects for it name AS9044. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.142.212.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.142.213.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.142.214.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.142.215.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.178.192.0/22 | Route objects for it name AS9044. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.178.192.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.178.193.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.178.194.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 185.178.195.0/24 | No route object for it. Add a route object with origin AS207143 in the RIR database for the space. |
| Route object: none | 193.135.58.0/24 | Route objects for it name AS9044. Add a route object with origin AS207143 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207143 whose prefix no peer sees AS207143 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.131.255.0/24 | RIPE | Valid |
| 95.36.100.0/22 | 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.