Network · data from 2026-11-12
AS40526 Gap, Inc. Direct
Registry name: THE-GAP-INC - Gap, Inc. Direct, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40526, 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.
| 206.16.32.0/24 | No ROA | Nonecovered by 206.16.32.0/22 | 668 99% |
| 103.205.184.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.103.113.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 8.45.104.0/24 | Valid | Nonecovered by 8.45.104.0/22 | 656 97% |
| 8.45.105.0/24 | Valid | Nonecovered by 8.45.104.0/22 | 656 97% |
| 8.21.68.0/22 | Valid | RIR databaseARIN, RADB | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS40526: AS-GAP. 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 (AS40526 isn't in the set, or no route object for AS40526 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 | AS40526 in it | Not covered |
|---|---|---|---|---|---|
| AS-GAP | RADB | 3 | 1 | 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 20 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: RIR1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.16.32.0/24 | No ROA covers it. Add a ROA for AS40526, maxLength 24. |
| Route object: none | 206.16.32.0/24 | No route object for it. A route object for 206.16.32.0/22 with origin AS40526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40526 in the RIR database for the space. |
| ROA: none | 103.205.184.0/24 | No ROA covers it. Add a ROA for AS40526, maxLength 24. |
| Route object: RIR | 103.205.184.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.103.113.0/24 | No ROA covers it. Add a ROA for AS40526, maxLength 24. |
| Route object: none | 8.45.104.0/24 | No route object for it. A route object for 8.45.104.0/22 with origin AS40526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40526 in the RIR database for the space. |
| Route object: none | 8.45.105.0/24 | No route object for it. A route object for 8.45.104.0/22 with origin AS40526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40526 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40526 whose prefix no peer sees AS40526 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.18.111.0/24 | RADB | No ROA |
| 8.45.104.0/22 | ARIN, RADB | Valid |
| 38.77.207.0/24 | RADB | No ROA |
| 38.134.117.0/24 | RADB | No ROA |
| 65.161.240.0/24 | RADB | No ROA |
| 70.42.137.0/24 | RADB | No ROA |
| 103.87.132.0/22 | RADB | No ROA |
| 162.246.240.0/20 | RIPE-NONAUTH | No ROA |
| 185.167.168.0/22 | RADB | No ROA |
| 185.167.168.0/24 | RADB | No ROA |
| 193.240.32.0/24 | RADB, RIPE | No ROA |
| 198.153.202.0/24 | RADB | No ROA |
| 206.16.32.0/22 | 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.