Network · data from 2026-11-12
AS133591 LIONET ONLINE
Registry name: LIONETVIP-AS-IN - LIONET ONLINE PVT LTD, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133591, 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.
| 154.18.164.0/24 | No ROA | Nonecovered by 154.18.164.0/22 | 10 1%low visibility |
| 154.18.165.0/24 | No ROA | Nonecovered by 154.18.164.0/22 | 10 1%low visibility |
| 154.18.166.0/24 | No ROA | Nonecovered by 154.18.164.0/22 | 10 1%low visibility |
| 154.18.167.0/24 | No ROA | Nonecovered by 154.18.164.0/22 | 10 1%low visibility |
| 2001:df1:f2c0::/48 | No ROA | RIR databaseAPNIC | 633 100% |
| 154.18.164.0/22 | No ROA | RIR databaseARIN | 10 1%low visibility |
| 103.154.27.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.181.7.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.154.26.0/24 | Valid | RIR databaseAPNIC | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS133591: AS133591:AS-LIONETVIP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133591 isn't in the set, or no route object for AS133591 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS133591 in it | Not covered |
|---|---|---|---|---|---|
| AS133591:AS-LIONETVIP | APNIC | 10 | 1 | Yes | 0 |
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.
- ROA: none6
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.18.164.0/24 | No ROA covers it. Add a ROA for AS133591, maxLength 24. |
| Route object: none | 154.18.164.0/24 | No route object for it. A route object for 154.18.164.0/22 with origin AS133591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133591 in the RIR database for the space. |
| ROA: none | 154.18.165.0/24 | No ROA covers it. Add a ROA for AS133591, maxLength 24. |
| Route object: none | 154.18.165.0/24 | No route object for it. A route object for 154.18.164.0/22 with origin AS133591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133591 in the RIR database for the space. |
| ROA: none | 154.18.166.0/24 | No ROA covers it. Add a ROA for AS133591, maxLength 24. |
| Route object: none | 154.18.166.0/24 | No route object for it. A route object for 154.18.164.0/22 with origin AS133591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133591 in the RIR database for the space. |
| ROA: none | 154.18.167.0/24 | No ROA covers it. Add a ROA for AS133591, maxLength 24. |
| Route object: none | 154.18.167.0/24 | No route object for it. A route object for 154.18.164.0/22 with origin AS133591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133591 in the RIR database for the space. |
| ROA: none | 2001:df1:f2c0::/48 | No ROA covers it. Add a ROA for AS133591, maxLength 48. |
| ROA: none | 154.18.164.0/22 | No ROA covers it. Add a ROA for AS133591, maxLength 22. |
Route objects not announced
Route objects with origin AS133591 whose prefix no peer sees AS133591 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 165.99.133.0/24 | APNIC | 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.