Network · data from 2026-11-12
AS54339
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54339, 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.185.86.0/23 | No ROA | Other IRR onlyRADB | 669 99% |
| 77.47.180.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 212.111.211.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.111.218.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
AS54339 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 36 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.185.86.0/23 | No ROA covers it. Add a ROA for AS54339, maxLength 23. |
| Route object: RIR | 89.185.86.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54339 whose prefix no peer sees AS54339 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.182.207.0/24 | RADB, RIPE | Valid |
| 62.112.206.0/24 | RADB, RIPE | Valid |
| 64.253.93.0/24 | ARIN, RADB | Valid |
| 67.210.102.0/24 | ARIN, RADB | Valid |
| 77.242.157.0/24 | RADB, RIPE | Valid |
| 84.55.23.0/24 | RADB, RIPE | Valid |
| 85.208.46.0/24 | RADB, RIPE | Valid |
| 85.239.144.0/22 | RADB | No ROA |
| 88.209.220.0/24 | RADB, RIPE | Valid |
| 89.42.92.0/24 | RADB, RIPE | Valid |
| 89.42.93.0/24 | RADB, RIPE | Valid |
| 89.43.142.0/24 | RADB, RIPE | Valid |
| 89.46.4.0/24 | RADB, RIPE | Valid |
| 89.47.123.0/24 | RADB, RIPE | Valid |
| 89.47.124.0/24 | RADB, RIPE | Valid |
| 92.113.9.0/24 | RADB, RIPE | Valid |
| 96.43.110.0/23 | ARIN, RADB | Valid |
| 102.129.157.0/24 | AFRINIC, RADB | Valid |
| 109.172.74.0/23 | RADB | No ROA |
| 157.254.28.0/24 | ARIN, RADB | Valid |
| 157.254.31.0/24 | ARIN, RADB | Valid |
| 157.254.34.0/23 | ARIN, RADB | Valid |
| 185.54.14.0/23 | RADB, RIPE | Valid |
| 185.194.29.0/24 | RADB, RIPE | Valid |
| 192.177.41.0/24 | ARIN, RADB | Valid |
| 192.177.63.0/24 | ARIN, RADB | Valid |
| 192.228.113.0/24 | ARIN, RADB | Valid |
| 192.228.126.0/23 | ARIN, RADB | Valid |
| 193.109.160.0/22 | RADB | No ROA |
| 193.109.160.0/23 | RADB | No ROA |
| 193.109.162.0/23 | RADB | No ROA |
| 193.149.179.0/24 | RADB, RIPE | Valid |
| 194.53.188.0/22 | RADB | Valid |
| 194.179.136.0/23 | RADB, 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.