Network · data from 2026-11-12
AS197549 DE-TopColo GHOSTnet GmbH
Registry name: DE-TopColo GHOSTnet GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197549, 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.
| 89.144.0.0/18 | Valid | Other origin only | 2 0%low visibility |
| 85.93.0.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 94.249.222.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 217.69.175.0/24 | Valid | RIR databaseRIPE | 668 99% |
AS-SET
AS197549 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 6 are in fix.csv.
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.144.0.0/18 | Route objects for it name AS12586. Add a route object with origin AS197549 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197549 whose prefix no peer sees AS197549 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.249.218.0/23 | RIPE | Valid |
| 94.249.234.0/23 | RIPE | Invalid: origin |
| 2a00:cdc0::/32 | RIPE | Invalid: origin |
| 2a00:cdc0:0:7::/64 | RIPE | Invalid: origin |
| 2a00:cdc0:10::/48 | RIPE | Invalid: origin |
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.