Network · data from 2026-11-12
AS210000 TwentyWAN Network
Registry name: TwentyWAN-Networks TwentyWAN MB, LT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210000, 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.
| 160.250.164.0/24 | Valid | None | 671 100% |
| 160.250.165.0/24 | Valid | None | 671 100% |
| 163.61.43.0/24 | Valid | None | 671 100% |
| 163.61.42.0/24 | Valid | None | 668 99% |
| 2602:faf4:1::/48 | Valid | Nonecovered by 2602:faf4::/40 | 635 100% |
| 23.128.140.0/24 | Valid | RIR databaseARIN | 671 100% |
| 23.142.145.0/24 | Valid | RIR databaseARIN | 671 100% |
| 31.41.34.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 177.177.77.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2602:f7b3::/40 | Valid | RIR databaseARIN | 635 100% |
| 2602:faf4::/40 | Valid | RIR databaseARIN | 635 100% |
| 2a12:3fc1:1001::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a12:3fc1:1002::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS210000: AS210000:AS-21WAN. 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 (AS210000 isn't in the set, or no route object for AS210000 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 | AS210000 in it | Not covered |
|---|---|---|---|---|---|
| AS210000:AS-21WAN | RIPE4 member sets in no database: AS-ZH-NET, AS150249:AS-ATHARVA, AS199605:AS-JSMSR-NETWORK, AS200105:AS-HK | 128 | 36 | Yes | 4 |
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 13 are in fix.csv.
- Route object: none5
- AS-SET: missing member4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 160.250.164.0/24 | No route object for it. Add a route object with origin AS210000 in the RIR database for the space. |
| Route object: none | 160.250.165.0/24 | No route object for it. Add a route object with origin AS210000 in the RIR database for the space. |
| Route object: none | 163.61.43.0/24 | No route object for it. Add a route object with origin AS210000 in the RIR database for the space. |
| Route object: none | 163.61.42.0/24 | No route object for it. Add a route object with origin AS210000 in the RIR database for the space. |
| Route object: none | 2602:faf4:1::/48 | No route object for it. A route object for 2602:faf4::/40 with origin AS210000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210000 in the RIR database for the space. |
| AS-SET: missing member | AS210000:AS-21WAN | AS210000:AS-21WAN (RIPE) lists AS-ZH-NET; no IRR database read has it. |
| AS-SET: missing member | AS210000:AS-21WAN | AS210000:AS-21WAN (RIPE) lists AS150249:AS-ATHARVA; no IRR database read has it. |
| AS-SET: missing member | AS210000:AS-21WAN | AS210000:AS-21WAN (RIPE) lists AS199605:AS-JSMSR-NETWORK; no IRR database read has it. |
| AS-SET: missing member | AS210000:AS-21WAN | AS210000:AS-21WAN (RIPE) lists AS200105:AS-HK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS210000 whose prefix no peer sees AS210000 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.191.8.0/24 | ARIN | Valid |
| 2001:470:299::/48 | ARIN | Valid |
| 2001:470:656::/48 | ARIN | Valid |
| 2a12:3fc1:2001::/48 | RIPE | 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.