Network · data from 2026-11-12
AS213549 SATISFYHOST
Registry name: SATISFYHOST SATISFYHOST LTD, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213549, 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:7581:9f47::/48 | Valid | None | 635 100% |
| 165.99.164.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.14.22.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 2a14:7581:9f43::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a14:7581:9f44::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS213549'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 6 are in fix.csv.
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a14:7581:9f47::/48 | No route object for it. Add a route object with origin AS213549 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213549 whose prefix no peer sees AS213549 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.202.194.0/24 | RADB, RIPE | Valid |
| 165.99.164.0/25 | APNIC | Valid |
| 165.99.164.128/25 | APNIC | Valid |
| 2a14:7581:fe9::/48 | RIPE | Valid |
| 2a14:7581:9f40::/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.