Network · data from 2026-11-12
AS200367 Ntens-AS Ntens LTD
Registry name: Ntens-AS Ntens LTD, CY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200367, 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.
| 196.196.102.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 87.58.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.108.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.205.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.36.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.124.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.124.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.124.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.152.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 209.131.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.12.219.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.43.149.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.147.14.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS200367 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: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.196.102.0/24 | No ROA covers it. Add a ROA for AS200367, maxLength 24. |
| Route object: RIR | 196.196.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200367 whose prefix no peer sees AS200367 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.58.212.0/24 | RIPE | Valid |
| 104.224.46.0/24 | ARIN | Valid |
| 212.193.28.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.