Network · data from 2026-11-12
AS51444 IT-LITE-NET IT Lite LLC
Registry name: IT-LITE-NET IT Lite LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51444, 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.218.248.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.218.249.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.218.250.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.218.251.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.170.164.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.170.165.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.227.36.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.227.37.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.227.38.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.227.39.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 37.18.2.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 37.18.3.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 37.18.83.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 37.230.212.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 37.230.213.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS51444 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 15 are in fix.csv.
- ROA: none15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.218.248.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 91.218.249.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 91.218.250.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 91.218.251.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 178.170.164.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 178.170.165.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 185.227.36.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 185.227.37.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 185.227.38.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 185.227.39.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 37.18.2.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 37.18.3.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 37.18.83.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 37.230.212.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
| ROA: none | 37.230.213.0/24 | No ROA covers it. Add a ROA for AS51444, maxLength 24. |
Route objects not announced
Every route object with origin AS51444 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.