Network · data from 2026-11-12
AS263684 Internet Services SA - 263684
Registry name: AS263684 - Internet Services S.A., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263684, 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.10.112.0/22 | No ROA | Nonecovered by 38.10.112.0/20 | 671 100% |
| 38.10.118.0/23 | No ROA | Nonecovered by 38.10.112.0/20 | 671 100% |
| 38.10.116.0/24 | No ROA | Nonecovered by 38.10.112.0/20 | 670 100% |
| 200.0.208.0/21 | No ROA | None | 669 99% |
| 38.10.118.0/24 | No ROA | Nonecovered by 38.10.112.0/20 | 2 0%low visibility |
| 45.224.8.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 170.244.56.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 200.115.24.0/21 | Valid | RIR databaseLACNIC | 670 100% |
| 2803:e900::/32 | Valid | RIR databaseLACNIC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS263684: AS263684:AS-ISS. 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 (AS263684 isn't in the set, or no route object for AS263684 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 | AS263684 in it | Not covered |
|---|---|---|---|---|---|
| AS263684:AS-ISS | LACNIC | 8 | 2 | Yes | 1 |
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 13 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.10.112.0/22 | No ROA covers it. Add a ROA for AS263684, maxLength 22. |
| Route object: none | 38.10.112.0/22 | No route object for it. A route object for 38.10.112.0/20 with origin AS263684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263684 in the RIR database for the space. |
| ROA: none | 38.10.118.0/23 | No ROA covers it. Add a ROA for AS263684, maxLength 23. |
| Route object: none | 38.10.118.0/23 | No route object for it. A route object for 38.10.112.0/20 with origin AS263684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263684 in the RIR database for the space. |
| ROA: none | 38.10.116.0/24 | No ROA covers it. Add a ROA for AS263684, maxLength 24. |
| Route object: none | 38.10.116.0/24 | No route object for it. A route object for 38.10.112.0/20 with origin AS263684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263684 in the RIR database for the space. |
| ROA: none | 200.0.208.0/21 | No ROA covers it. Add a ROA for AS263684, maxLength 21. |
| Route object: none | 200.0.208.0/21 | No route object for it. Add a route object with origin AS263684 in the RIR database for the space. |
| ROA: none | 38.10.118.0/24 | No ROA covers it. Add a ROA for AS263684, maxLength 24. |
| Route object: none | 38.10.118.0/24 | No route object for it. A route object for 38.10.112.0/20 with origin AS263684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263684 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263684 whose prefix no peer sees AS263684 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.10.112.0/20 | RADB | No ROA |
| 200.115.25.0/24 | LACNIC | Valid |
| 200.115.26.0/24 | 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.