Network · data from 2026-11-12
AS10697 Interlink SRL
Registry name: AS10697 - INTERLINK SA, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10697, 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.
| 200.50.161.0/24 | No ROA | Nonecovered by 200.50.160.0/19 | 667 99% |
| 200.50.164.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 200.50.173.0/24 | Valid | RIR databaseLACNIC | 669 99% |
AS-SET
AS10697'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 11 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.50.161.0/24 | No ROA covers it. Add a ROA for AS10697, maxLength 24. |
| Route object: none | 200.50.161.0/24 | No route object for it. A route object for 200.50.160.0/19 with origin AS10697 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10697 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10697 whose prefix no peer sees AS10697 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.110.224.0/19 | RADB | No ROA |
| 190.114.96.0/19 | RADB | No ROA |
| 200.50.160.0/19 | RADB | No ROA |
| 200.123.32.0/19 | RADB | No ROA |
| 201.234.93.0/24 | LACNIC | Valid |
| 206.221.80.0/20 | LACNIC | Valid |
| 2800:820::/32 | LACNIC | Valid |
| 2800:820:1::/48 | LACNIC | Valid |
| 2803:7e80::/32 | LACNIC | 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.