Network · data from 2026-11-12
AS40528 ICANN AS40528
Registry name: ICANN-LAX - ICANN, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40528, 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.
| 2602:800:9000::/48 | No ROA | None | 635 100% |
| 192.0.32.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.0.32.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.4.28.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.77.188.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 2602:800:900e::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 2620:0:2d0::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 192.0.43.0/24 | No ROA | Other IRR onlyRADB | 129 19% |
| 2001:500:88::/48 | No ROA | Other IRR onlyRADB | 113 18% |
AS-SET
PeeringDB's irr_as_set for AS40528: AS-ICANN. 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 (AS40528 isn't in the set, or no route object for AS40528 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 | AS40528 in it | Not covered |
|---|---|---|---|---|---|
| AS-ICANN | RADB | 18 | 4 | Yes | 1 |
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 20 are in fix.csv.
- ROA: none9
- Route object: none1
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:800:9000::/48 | No ROA covers it. Add a ROA for AS40528, maxLength 48. |
| Route object: none | 2602:800:9000::/48 | No route object for it. Add a route object with origin AS40528 in the RIR database for the space. |
| ROA: none | 192.0.32.0/22 | No ROA covers it. Add a ROA for AS40528, maxLength 22. |
| Route object: RIR | 192.0.32.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.0.32.0/24 | No ROA covers it. Add a ROA for AS40528, maxLength 24. |
| Route object: RIR | 192.0.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.4.28.0/24 | No ROA covers it. Add a ROA for AS40528, maxLength 24. |
| Route object: RIR | 199.4.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.77.188.0/22 | No ROA covers it. Add a ROA for AS40528, maxLength 22. |
| Route object: RIR | 208.77.188.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:800:900e::/48 | No ROA covers it. Add a ROA for AS40528, maxLength 48. |
| Route object: RIR | 2602:800:900e::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2620:0:2d0::/48 | No ROA covers it. Add a ROA for AS40528, maxLength 48. |
| Route object: RIR | 2620:0:2d0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.0.43.0/24 | No ROA covers it. Add a ROA for AS40528, maxLength 24. |
| Route object: RIR | 192.0.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:500:88::/48 | No ROA covers it. Add a ROA for AS40528, maxLength 48. |
| Route object: RIR | 2001:500:88::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40528 whose prefix no peer sees AS40528 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.7.81.0/24 | RADB | No ROA |
| 2001:500:11::/48 | RADB | 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.