Network · data from 2026-11-12
AS271933 AIRMAXTELECOM SOLUCIONES TECNOLOGICAS
Registry name: AS271933 - AIRMAXTELECOM SOLUCIONES TECNOLOGICAS S.A., EC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271933, 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:c420:3000::/40 | Valid | Nonecovered by 2803:c420::/32 | 633 100% |
| 2803:c420:3400::/40 | Valid | Nonecovered by 2803:c420::/32 | 633 100% |
| 2803:c420:2400::/40 | Valid | Nonecovered by 2803:c420::/32 | 2 0%low visibility |
| 154.50.102.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 38.100.9.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 45.70.12.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.70.13.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.70.14.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.70.15.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 2803:c420::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS271933: AS271933. 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 (AS271933 isn't in the set, or no route object for AS271933 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 | AS271933 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS271933 | A single AS number, not a set: AS271933 (this network), 9 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 5 are in fix.csv.
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:c420:3000::/40 | No route object for it. A route object for 2803:c420::/32 with origin AS271933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271933 in the RIR database for the space. |
| Route object: none | 2803:c420:3400::/40 | No route object for it. A route object for 2803:c420::/32 with origin AS271933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271933 in the RIR database for the space. |
| Route object: none | 2803:c420:2400::/40 | No route object for it. A route object for 2803:c420::/32 with origin AS271933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271933 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271933 whose prefix no peer sees AS271933 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.70.12.0/22 | LACNIC, RADB | Valid |
| 45.70.12.0/23 | 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.