Network · data from 2026-11-12
AS270764 Ecxon Datacenter
Registry name: AS270764 - Ecxon Datacenter LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270764, 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.
| 189.127.164.0/24 | Valid | Other IRR onlyRADB, TC | 673 100% |
| 189.127.165.0/24 | Valid | Other IRR onlyRADB, TC | 673 100% |
| 45.40.99.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:7110:4000::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:7110:5100::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:7110:7100::/48 | Valid | Other IRR onlyTC | 634 100% |
| 172.84.94.0/24 | Valid | RIR databaseARIN | 673 100% |
| 181.215.236.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 181.215.253.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 181.215.254.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 104.234.119.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS270764: AS270764:AS-ALL. 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 (AS270764 isn't in the set, or no route object for AS270764 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 | AS270764 in it | Not covered |
|---|---|---|---|---|---|
| AS270764:AS-ALL | TC | 2 | 2 | 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 18 are in fix.csv.
- Route object: RIR6
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 189.127.164.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.165.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.40.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7110:4000::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7110:5100::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7110:7100::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270764 whose prefix no peer sees AS270764 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.255.171.0/24 | RADB, RIPE | Valid |
| 189.127.164.0/23 | RADB, TC | No ROA |
| 198.1.195.0/24 | ARIN, RADB | Valid |
| 2804:7110::/32 | RADB, TC | No ROA |
| 2804:7110:1000::/48 | TC | Valid |
| 2804:7110:3000::/48 | TC | Valid |
| 2804:7110:3100::/48 | TC | Valid |
| 2804:7110:4000::/40 | TC | No ROA |
| 2804:7110:5100::/40 | TC | Valid |
| 2804:7110:6000::/48 | TC | Valid |
| 2804:7110:6100::/48 | TC | Valid |
| 2804:7110:7100::/40 | TC | 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.