Network · data from 2026-11-12
AS269931 WIRELESS MULTI SERVICE VARGAS CABRERA
Registry name: AS269931 - WIRELESS MULTI SERVICE VARGAS CABRERA, S. R. L, DO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269931, 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:f2e0:8009::/48 | Valid | Nonecovered by 2803:f2e0::/32 | 634 100% |
| 2803:f2e0:ff76::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 190.110.34.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 190.110.35.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.125.169.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.125.170.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.125.168.0/24 | Valid | RIR databaseLACNIC | 668 99% |
| 200.125.171.0/24 | Valid | RIR databaseLACNIC | 668 99% |
| 2803:f2e0::/32 | Valid | RIR databaseLACNIC, RADB | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS269931: AS269931:AS-CLIENTES. 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 (AS269931 isn't in the set, or no route object for AS269931 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 | AS269931 in it | Not covered |
|---|---|---|---|---|---|
| AS269931:AS-CLIENTES | LACNIC | 45 | 1 | No | 9 |
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 6 are in fix.csv.
- Route object: none1
- Route object: RIR1
- AS-SET: own ASN1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:f2e0:8009::/48 | No route object for it. A route object for 2803:f2e0::/32 with origin AS269931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269931 in the RIR database for the space. |
| Route object: RIR | 2803:f2e0:ff76::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS269931:AS-CLIENTES | AS269931 isn't in AS269931:AS-CLIENTES (LACNIC) once expanded. Add AS269931 to it. |
Route objects not announced
Route objects with origin AS269931 whose prefix no peer sees AS269931 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.10.247.0/24 | RADB | No ROA |
| 106.0.206.0/23 | RADB | No ROA |
| 200.125.168.0/22 | 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.