Network · data from 2026-11-12
AS213460 simplisticnodeus Lonex Group Limited
Registry name: simplisticnodeus Lonex Group Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213460, 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.
| 91.124.123.0/24 | Invalid: origin | None | 3 0%low visibility |
| 82.153.220.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 168.222.62.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a13:9500:1b0::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS213460 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 91.124.123.0/24 | ROAs covering it name AS834, not AS213460. If AS213460 should announce it, add a ROA for AS213460. |
| Route object: none | 91.124.123.0/24 | No route object for it. Add a route object with origin AS213460 in the RIR database for the space. |
| Route object: RIR | 82.153.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS213460 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.