Network · data from 2026-11-12
AS62110 LEADERPICI-AS Leader PI CI Ltd.
Registry name: LEADERPICI-AS Leader PI CI Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62110, 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.
| 151.237.79.56/32 | Invalid: maxLength | Nonecovered by 151.237.79.0/24 | 3 0%low visibility |
| 151.237.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS62110 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: maxLength1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 151.237.79.56/32 | ROA 151.237.78.0/23 AS62110 has maxLength 23; ROA 151.237.79.0/24 AS62110 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 151.237.79.56/32. |
| Route object: none | 151.237.79.56/32 | No route object for it. A route object for 151.237.79.0/24 with origin AS62110 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62110 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62110 whose prefix no peer sees AS62110 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 151.237.78.0/23 | 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.