Network · data from 2026-11-12
AS19504 WTCC - WTC Communications, Inc.
Registry name: WTCC - WTC Communications, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19504, 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.
| 107.151.63.0/24 | Valid | Nonecovered by 107.151.48.0/20 | 673 100% |
| 216.147.230.0/24 | Valid | Nonecovered by 216.147.224.0/21 | 673 100% |
| 216.147.236.0/22 | Valid | Nonecovered by 216.147.232.0/21 | 673 100% |
| 68.171.184.0/21 | Valid | RIR databaseARIN | 673 100% |
| 206.168.16.0/21 | Valid | RIR databaseARIN | 673 100% |
| 206.168.24.0/21 | Valid | RIR databaseARIN | 673 100% |
| 216.122.156.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.147.232.0/21 | Valid | RIR databaseARIN | 673 100% |
| 66.109.112.0/22 | Valid | RIR databaseARIN | 671 100% |
| 104.200.208.0/22 | Valid | RIR databaseARIN | 671 100% |
| 104.200.212.0/22 | Valid | RIR databaseARIN | 671 100% |
| 64.6.112.0/20 | Valid | RIR databaseARIN | 670 100% |
| 66.109.112.0/21 | Valid | RIR databaseARIN | 670 100% |
| 68.171.176.0/20 | Valid | RIR databaseARIN | 670 100% |
| 104.200.208.0/21 | Valid | RIR databaseARIN | 670 100% |
| 107.151.48.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 206.168.16.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 216.122.152.0/21 | Valid | RIR databaseARIN | 670 100% |
| 216.147.224.0/20 | Valid | RIR databaseARIN | 670 100% |
| 216.147.224.0/21 | Valid | RIR databaseARIN | 670 100% |
| 64.6.112.0/21 | Valid | RIR databaseARIN | 669 99% |
| 64.6.120.0/21 | Valid | RIR databaseARIN | 669 99% |
| 66.109.116.0/22 | Valid | RIR databaseARIN | 669 99% |
| 68.171.176.0/21 | Valid | RIR databaseARIN | 669 99% |
| 216.122.152.0/22 | Valid | RIR databaseARIN | 669 99% |
AS-SET
AS19504 isn't in PeeringDB, where networks name their AS-SET.
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 7 are in fix.csv.
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 107.151.63.0/24 | No route object for it. A route object for 107.151.48.0/20 with origin AS19504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19504 in the RIR database for the space. |
| Route object: none | 216.147.230.0/24 | No route object for it. A route object for 216.147.224.0/21 with origin AS19504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19504 in the RIR database for the space. |
| Route object: none | 216.147.236.0/22 | No route object for it. A route object for 216.147.232.0/21 with origin AS19504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19504 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19504 whose prefix no peer sees AS19504 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.6.120.0/22 | ARIN | Valid |
| 64.6.128.0/20 | RADB | No ROA |
| 104.200.214.0/23 | ARIN | Valid |
| 2604:1c0::/32 | ARIN | 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.