Network · data from 2026-11-12
AS8416 Infoline
Registry name: INFOLINE-AS InfoLada Ltd, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8416, 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.
| 81.23.176.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 178.163.0.0/17 | No ROA | RIR databaseRIPE | 673 100% |
| 185.134.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 217.113.112.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 2a0a:5900::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS8416's PeeringDB record names no 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: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.23.176.0/20 | No ROA covers it. Add a ROA for AS8416, maxLength 20. |
| ROA: none | 178.163.0.0/17 | No ROA covers it. Add a ROA for AS8416, maxLength 17. |
| ROA: none | 185.134.36.0/22 | No ROA covers it. Add a ROA for AS8416, maxLength 22. |
| ROA: none | 217.113.112.0/20 | No ROA covers it. Add a ROA for AS8416, maxLength 20. |
| ROA: none | 2a0a:5900::/29 | No ROA covers it. Add a ROA for AS8416, maxLength 29. |
Route objects not announced
Every route object with origin AS8416 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.