Network · data from 2026-11-12
AS265548 WCD, S.A. DE C.V.
Registry name: AS265548 - WCD, S.A. DE C.V., MX · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265548, 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.
| 45.232.252.0/24 | Valid | Nonecovered by 45.232.252.0/22 | 670 100% |
| 45.232.253.0/24 | Valid | Nonecovered by 45.232.252.0/22 | 670 100% |
| 45.232.254.0/24 | Valid | Nonecovered by 45.232.252.0/22 | 670 100% |
| 2806:2fc:20::/43 | Valid | Nonecovered by 2806:2fc::/32 | 635 100% |
| 2806:2fc:30::/44 | Valid | Nonecovered by 2806:2fc::/32 | 635 100% |
| 2806:2fc:20::/44 | Valid | Nonecovered by 2806:2fc::/32 | 634 100% |
| 45.232.255.0/24 | Valid | Other IRR onlyRADB | 665 99% |
| 45.232.252.0/22 | Valid | RIR databaseLACNIC, RADB | 666 99% |
| 193.149.142.0/24 | Valid | RIR databaseLACNIC | 666 99% |
AS-SET
PeeringDB's irr_as_set for AS265548: LACNIC::AS265548. 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 (AS265548 isn't in the set, or no route object for AS265548 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 | AS265548 in it | Not covered | |
|---|---|---|---|---|---|---|
| LACNIC::AS265548 | A single AS number, not a set: AS265548 (this network), 4 route objects. | |||||
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: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.232.252.0/24 | No route object for it. A route object for 45.232.252.0/22 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: none | 45.232.253.0/24 | No route object for it. A route object for 45.232.252.0/22 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: none | 45.232.254.0/24 | No route object for it. A route object for 45.232.252.0/22 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: none | 2806:2fc:20::/43 | No route object for it. A route object for 2806:2fc::/32 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: none | 2806:2fc:30::/44 | No route object for it. A route object for 2806:2fc::/32 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: none | 2806:2fc:20::/44 | No route object for it. A route object for 2806:2fc::/32 with origin AS265548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265548 in the RIR database for the space. |
| Route object: RIR | 45.232.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265548 whose prefix no peer sees AS265548 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2806:2fc::/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.