Network · data from 2026-11-12
AS61506 Insacom y Cia. Limitada
Registry name: AS61506 - INSACOM SpA, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61506, 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.
| 2803:4640:15f::/48 | Valid | Nonecovered by 2803:4640::/32 | 605 95% |
| 2803:4640:dca5::/48 | Valid | Nonecovered by 2803:4640::/32 | 605 95% |
| 138.204.229.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 138.204.231.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 138.204.228.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 138.204.230.0/24 | Valid | Other IRR onlyRADB | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS61506: AS61506:AS-INSACOM. 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 (AS61506 isn't in the set, or no route object for AS61506 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 | AS61506 in it | Not covered |
|---|---|---|---|---|---|
| AS61506:AS-INSACOM | LACNIC | 1 | 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 8 are in fix.csv.
- Route object: none2
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:4640:15f::/48 | No route object for it. A route object for 2803:4640::/32 with origin AS61506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61506 in the RIR database for the space. |
| Route object: none | 2803:4640:dca5::/48 | No route object for it. A route object for 2803:4640::/32 with origin AS61506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61506 in the RIR database for the space. |
| Route object: RIR | 138.204.229.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.204.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.204.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.204.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61506 whose prefix no peer sees AS61506 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.204.228.0/22 | LACNIC, NTTCOM, RADB | Valid |
| 2803:4640::/32 | LACNIC, RADB | 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.