Network · data from 2026-11-12
AS265757 Intersur Limitada
Registry name: AS265757 - Intersur Limitada, CL · PeeringDB
17IPv4 routes
100.0% RPKI valid · 17.6% with a route object
10IPv6 routes
100.0% RPKI valid · 10.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
23 with no route object for this origin
9Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS265757, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS265757, 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.
| 38.250.108.0/23 | Valid | Nonecovered by 38.250.108.0/22 | 670 100% |
| 38.250.110.0/23 | Valid | Nonecovered by 38.250.108.0/22 | 670 100% |
| 38.250.111.0/24 | Valid | Nonecovered by 38.250.108.0/22 | 670 100% |
| 131.196.176.0/23 | Valid | Nonecovered by 131.196.176.0/22 | 670 100% |
| 131.196.178.0/23 | Valid | Nonecovered by 131.196.176.0/22 | 670 100% |
| 2803:9bc0:100::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:200::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:300::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:400::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:500::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:600::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:700::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:800::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 2803:9bc0:900::/40 | Valid | Nonecovered by 2803:9bc0::/32 | 635 100% |
| 38.250.108.0/24 | Valid | Nonecovered by 38.250.108.0/22 | 12 2%low visibility |
| 38.250.109.0/24 | Valid | Nonecovered by 38.250.108.0/22 | 12 2%low visibility |
| 38.250.110.0/24 | Valid | Nonecovered by 38.250.108.0/22 | 12 2%low visibility |
| 45.162.194.0/24 | Valid | Nonecovered by 45.162.194.0/23 | 12 2%low visibility |
| 45.162.195.0/24 | Valid | Nonecovered by 45.162.194.0/23 | 12 2%low visibility |
| 131.196.176.0/24 | Valid | Nonecovered by 131.196.176.0/22 | 12 2%low visibility |
| 131.196.177.0/24 | Valid | Nonecovered by 131.196.176.0/22 | 12 2%low visibility |
| 131.196.178.0/24 | Valid | Nonecovered by 131.196.176.0/22 | 12 2%low visibility |
| 131.196.179.0/24 | Valid | Nonecovered by 131.196.176.0/22 | 12 2%low visibility |
| 38.250.108.0/22 | Valid | RIR databaseARIN | 670 100% |
| 45.162.194.0/23 | Valid | RIR databaseLACNIC | 670 100% |
| 131.196.176.0/22 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 2803:9bc0::/32 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS265757: AS265757:AS-INTERSUR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265757 isn't in the set, or no route object for AS265757 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS265757 in it | Not covered |
|---|---|---|---|---|---|
| AS265757:AS-INTERSUR | LACNIC | 10 | 1 | Yes | 0 |
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 23 are in fix.csv.
- Route object: none23
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.250.108.0/23 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 38.250.110.0/23 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 38.250.111.0/24 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.176.0/23 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.178.0/23 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:100::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:200::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:300::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:400::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:500::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:600::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:700::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:800::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 2803:9bc0:900::/40 | No route object for it. A route object for 2803:9bc0::/32 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 38.250.108.0/24 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 38.250.109.0/24 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 38.250.110.0/24 | No route object for it. A route object for 38.250.108.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 45.162.194.0/24 | No route object for it. A route object for 45.162.194.0/23 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 45.162.195.0/24 | No route object for it. A route object for 45.162.194.0/23 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.176.0/24 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.177.0/24 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.178.0/24 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
| Route object: none | 131.196.179.0/24 | No route object for it. A route object for 131.196.176.0/22 with origin AS265757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265757 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS265757 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.