Network · data from 2026-11-12
AS34806 ASLINE-AS ASLINE LIMITED
Registry name: ASLINE-AS ASLINE LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34806, 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.
| 103.100.69.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS34806 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 11 are in fix.csv.
- Route object: RIR1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.100.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34806 whose prefix no peer sees AS34806 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 49.220.234.0/24 | RADB | No ROA |
| 61.29.193.0/24 | RADB | No ROA |
| 103.28.7.0/24 | RADB | No ROA |
| 103.134.145.0/24 | RADB | No ROA |
| 103.135.144.0/22 | RADB | No ROA |
| 119.27.239.0/24 | RADB | No ROA |
| 119.42.134.0/24 | RADB | No ROA |
| 123.99.190.0/24 | RADB | No ROA |
| 203.99.81.0/24 | RADB | No ROA |
| 2a0f:7a80::/29 | RADB | No ROA |
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.