Network · data from 2026-11-12
AS329562 SERVERLINK SOLUTIONS LIMITED
Registry name: SERVERLINK SOLUTIONS LIMITED - SERVERLINK SOLUTIONS LIMITED, KE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS329562, 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.
| 102.205.148.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.205.148.0/23 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.205.148.0/24 | Valid | RIR databaseAFRINIC | 109 16% |
| 102.205.149.0/24 | Valid | RIR databaseAFRINIC | 109 16% |
| 102.205.150.0/24 | Valid | RIR databaseAFRINIC | 109 16% |
| 102.205.151.0/24 | Valid | RIR databaseAFRINIC | 109 16% |
| 102.205.150.0/23 | Valid | RIR databaseAFRINIC | 2 0%low visibility |
AS-SET
AS329562's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS329562 is announced.
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.