Network · data from 2026-11-12
AS19122 eStruxture AS19122
Registry name: ESTRUXTURE-ON-19122 - eStruxture Data Centers Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19122, 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.
| 38.132.48.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.34.55.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 199.167.131.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 216.71.120.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 216.170.124.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 2602:fbb0::/36 | No ROA | RIR databaseARIN | 636 100% |
| 69.165.84.0/22 | Valid | RIR databaseARIN | 671 100% |
| 2605:9000:6::/48 | Valid | RIR databaseARIN | 636 100% |
| 2605:9000:c::/48 | Valid | RIR databaseARIN | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS19122: AS-ESTRUXTURE. 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 (AS19122 isn't in the set, or no route object for AS19122 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 | AS19122 in it | Not covered |
|---|---|---|---|---|---|
| AS-ESTRUXTURE | ARIN1 member set in no database: AS-MEDIA-HOSTS | 55 | 5 | 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 9 are in fix.csv.
- ROA: none6
- Route object: RIR1
- AS-SET: missing member1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.132.48.0/20 | No ROA covers it. Add a ROA for AS19122, maxLength 20. |
| Route object: RIR | 38.132.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.34.55.0/24 | No ROA covers it. Add a ROA for AS19122, maxLength 24. |
| ROA: none | 199.167.131.0/24 | No ROA covers it. Add a ROA for AS19122, maxLength 24. |
| ROA: none | 216.71.120.0/24 | No ROA covers it. Add a ROA for AS19122, maxLength 24. |
| ROA: none | 216.170.124.0/24 | No ROA covers it. Add a ROA for AS19122, maxLength 24. |
| ROA: none | 2602:fbb0::/36 | No ROA covers it. Add a ROA for AS19122, maxLength 36. |
| AS-SET: missing member | AS-ESTRUXTURE | AS-ESTRUXTURE (ARIN) lists AS-MEDIA-HOSTS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS19122 whose prefix no peer sees AS19122 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 208.90.28.0/23 | ARIN | No ROA |
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.