Network · data from 2026-11-12
AS212171 Local-as Local NCC Ltd.
Registry name: Local-as Local NCC Ltd., GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212171, 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.
| 185.69.120.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 185.199.196.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 185.207.14.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 5.253.57.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.207.14.0/24 | Valid | Nonecovered by 185.207.14.0/23 | 673 100% |
| 185.207.15.0/24 | Valid | Nonecovered by 185.207.14.0/23 | 673 100% |
| 92.118.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.118.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.118.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.118.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.118.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.166.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.166.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.166.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.166.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.86.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.86.62.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.86.63.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.86.64.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.145.12.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.91.100.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.91.101.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.91.102.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.91.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS212171 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 8 are in fix.csv.
- ROA: origin2
- ROA: none2
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.69.120.0/22 | ROAs covering it name AS213929, not AS212171. If AS212171 should announce it, add a ROA for AS212171. |
| Route object: none | 185.69.120.0/22 | Route objects for it name AS213929. Add a route object with origin AS212171 in the RIR database for the space. |
| ROA: origin | 185.199.196.0/22 | ROAs covering it name AS213929, not AS212171. If AS212171 should announce it, add a ROA for AS212171. |
| Route object: none | 185.199.196.0/22 | Route objects for it name AS213929. Add a route object with origin AS212171 in the RIR database for the space. |
| ROA: none | 185.207.14.0/23 | No ROA covers it. Add a ROA for AS212171, maxLength 23. |
| ROA: none | 5.253.57.0/24 | No ROA covers it. Add a ROA for AS212171, maxLength 24. |
| Route object: none | 185.207.14.0/24 | No route object for it. A route object for 185.207.14.0/23 with origin AS212171 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212171 in the RIR database for the space. |
| Route object: none | 185.207.15.0/24 | No route object for it. A route object for 185.207.14.0/23 with origin AS212171 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212171 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS212171 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.