Network · data from 2026-11-12
AS213694 INLAN-AS INLAN LLC
Registry name: INLAN-AS INLAN LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213694, 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.
| 193.178.236.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 45.66.251.0/24 | Valid | Nonecovered by 45.66.250.0/23 | 64 10%low visibility |
| 45.66.250.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 212.66.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.83.183.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS213694 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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.178.236.0/23 | No ROA covers it. Add a ROA for AS213694, maxLength 23. |
| Route object: none | 45.66.251.0/24 | No route object for it. A route object for 45.66.250.0/23 with origin AS213694 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213694 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213694 whose prefix no peer sees AS213694 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 176.124.24.0/23 | RIPE | Valid |
| 176.124.24.0/24 | RIPE | Valid |
| 176.124.25.0/24 | 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.