Network · data from 2026-11-12
AS7693 KSC Commercial Internet
Registry name: COMNET-TH - KSC Commercial Internet Co. Ltd., TH · PeeringDB
93IPv4 routes
95.7% RPKI valid · 97.8% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
2RPKI invalid
0 origin · 2 maxLength
2No ROA
2 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
193Route objects not announced
registered with origin AS7693, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS7693, 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.
| 202.44.144.34/32 | Invalid: maxLength | Nonecovered by 202.44.144.0/24 | 4 1%low visibility |
| 202.44.144.42/32 | Invalid: maxLength | Nonecovered by 202.44.144.0/24 | 4 1%low visibility |
| 202.0.117.0/24 | No ROA | Other IRR onlyRADB, REACH | 673 100% |
| 202.0.118.0/24 | No ROA | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 58.181.128.0/17 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.128.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.144.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.146.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 58.181.160.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.176.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.192.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.200.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 673 100% |
| 58.181.208.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.212.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 58.181.224.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.225.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 58.181.240.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 58.181.248.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 58.181.252.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.19.104.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 140.149.0.0/16 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 140.149.0.0/17 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 140.149.128.0/17 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.144.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.149.96.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.149.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.149.112.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.128.0/17 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.129.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.107.130.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.107.144.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.160.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.176.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.192.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.192.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.107.208.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.224.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.231.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.107.240.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.107.255.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.155.0.0/16 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.0.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.0.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.155.16.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.32.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.42.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.155.48.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.54.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.155.64.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.66.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 673 100% |
| 203.155.77.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.155.80.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.112.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.128.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.144.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.160.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.176.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.192.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.208.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.224.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.240.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.155.253.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.0.0/18 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.188.0.0/20 | Valid | RIR databaseAPNIC, RADB, REACH | 673 100% |
| 203.188.1.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.188.2.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.5.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.6.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.188.10.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.12.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.188.12.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.188.32.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.195.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.195.105.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.209.0.0/18 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.0.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.16.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.32.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.48.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.64.0/18 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.64.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.75.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.209.93.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.209.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.112.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 203.209.122.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.209.123.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.209.125.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.209.80.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
| 203.107.128.0/20 | Valid | RIR databaseAPNIC, RADB, REACH | 670 100% |
| 2405:a000::/32 | Valid | RIR databaseAPNIC, RADB | 633 100% |
| 2405:a000::/33 | Valid | RIR databaseAPNIC, RADB | 631 99% |
| 203.155.219.0/24 | Valid | RIR databaseAPNIC, RADB | 133 20% |
| 203.188.4.0/24 | Valid | RIR databaseAPNIC, RADB | 133 20% |
AS-SET
AS7693's PeeringDB record names no 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 201 are in fix.csv.
- ROA: maxLength2
- ROA: none2
- Route object: none2
- Route object: RIR2
- Route object: not announced193
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.44.144.34/32 | ROA 202.44.144.0/24 AS7693 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.44.144.34/32. |
| Route object: none | 202.44.144.34/32 | No route object for it. A route object for 202.44.144.0/24 with origin AS7693 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7693 in the RIR database for the space. |
| ROA: maxLength | 202.44.144.42/32 | ROA 202.44.144.0/24 AS7693 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 202.44.144.42/32. |
| Route object: none | 202.44.144.42/32 | No route object for it. A route object for 202.44.144.0/24 with origin AS7693 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS7693 in the RIR database for the space. |
| ROA: none | 202.0.117.0/24 | No ROA covers it. Add a ROA for AS7693, maxLength 24. |
| Route object: RIR | 202.0.117.0/24 | Route object only in RADB, REACH. Add it in the RIR database for the space. |
| ROA: none | 202.0.118.0/24 | No ROA covers it. Add a ROA for AS7693, maxLength 24. |
| Route object: RIR | 202.0.118.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7693 whose prefix no peer sees AS7693 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.179.0.0/16 | NTTCOM, REACH | No ROA |
| 168.120.0.0/18 | REACH | No ROA |
| 168.120.12.0/24 | REACH | No ROA |
| 168.120.13.0/24 | REACH | No ROA |
| 168.120.26.0/24 | REACH | No ROA |
| 168.120.27.0/24 | REACH | No ROA |
| 168.120.64.0/18 | REACH | No ROA |
| 168.120.64.0/24 | REACH | No ROA |
| 168.120.65.0/24 | REACH | No ROA |
| 168.120.66.0/24 | REACH | No ROA |
| 168.120.67.0/24 | REACH | No ROA |
| 168.120.68.0/24 | REACH | No ROA |
| 168.120.69.0/24 | REACH | No ROA |
| 168.120.70.0/24 | REACH | No ROA |
| 168.120.71.0/24 | REACH | No ROA |
| 168.120.72.0/24 | REACH | No ROA |
| 168.120.73.0/24 | REACH | No ROA |
| 168.120.74.0/24 | REACH | No ROA |
| 168.120.75.0/24 | REACH | No ROA |
| 168.120.76.0/24 | REACH | No ROA |
| 168.120.77.0/24 | REACH | No ROA |
| 168.120.78.0/24 | REACH | No ROA |
| 168.120.79.0/24 | REACH | No ROA |
| 168.120.80.0/24 | REACH | No ROA |
| 168.120.81.0/24 | REACH | No ROA |
| 168.120.82.0/24 | REACH | No ROA |
| 168.120.83.0/24 | REACH | No ROA |
| 168.120.84.0/24 | REACH | No ROA |
| 168.120.85.0/24 | REACH | No ROA |
| 168.120.86.0/24 | REACH | No ROA |
| 168.120.87.0/24 | REACH | No ROA |
| 168.120.88.0/24 | REACH | No ROA |
| 168.120.89.0/24 | REACH | No ROA |
| 168.120.90.0/24 | REACH | No ROA |
| 168.120.91.0/24 | REACH | No ROA |
| 168.120.92.0/24 | REACH | No ROA |
| 168.120.93.0/24 | REACH | No ROA |
| 168.120.94.0/24 | REACH | No ROA |
| 168.120.95.0/24 | REACH | No ROA |
| 168.120.96.0/24 | REACH | No ROA |
| 168.120.97.0/24 | REACH | No ROA |
| 168.120.98.0/24 | REACH | No ROA |
| 168.120.99.0/24 | REACH | No ROA |
| 168.120.100.0/24 | REACH | No ROA |
| 168.120.101.0/24 | REACH | No ROA |
| 168.120.102.0/24 | REACH | No ROA |
| 168.120.103.0/24 | REACH | No ROA |
| 168.120.104.0/24 | REACH | No ROA |
| 168.120.105.0/24 | REACH | No ROA |
| 168.120.106.0/24 | REACH | No ROA |
| 168.120.107.0/24 | REACH | No ROA |
| 168.120.108.0/24 | REACH | No ROA |
| 168.120.109.0/24 | REACH | No ROA |
| 168.120.110.0/24 | REACH | No ROA |
| 168.120.111.0/24 | REACH | No ROA |
| 168.120.112.0/24 | REACH | No ROA |
| 168.120.113.0/24 | REACH | No ROA |
| 168.120.114.0/24 | REACH | No ROA |
| 168.120.115.0/24 | REACH | No ROA |
| 168.120.116.0/22 | REACH | No ROA |
| 168.120.120.0/21 | REACH | No ROA |
| 192.41.170.0/24 | REACH | Invalid: origin |
| 198.49.112.0/23 | REACH | No ROA |
| 198.49.112.0/24 | REACH | No ROA |
| 198.49.113.0/24 | REACH | No ROA |
| 202.6.100.0/23 | REACH | No ROA |
| 202.8.25.0/24 | REACH | Invalid: origin |
| 202.8.78.0/23 | REACH | Invalid: origin |
| 202.8.78.0/24 | REACH | Invalid: origin |
| 202.8.79.0/24 | REACH | Invalid: origin |
| 202.20.105.0/24 | REACH | Invalid: origin |
| 202.22.8.0/21 | NTTCOM, REACH | No ROA |
| 202.28.24.0/22 | REACH | Invalid: origin |
| 202.28.25.0/24 | REACH | Invalid: origin |
| 202.28.26.0/24 | REACH | Invalid: origin |
| 202.28.27.0/24 | REACH | Invalid: origin |
| 202.28.128.0/21 | REACH | Invalid: origin |
| 202.28.136.0/21 | REACH | Invalid: origin |
| 202.28.144.0/21 | REACH | Invalid: origin |
| 202.28.152.0/21 | REACH | Invalid: origin |
| 202.28.160.0/21 | REACH | Invalid: origin |
| 202.28.168.0/21 | REACH | Invalid: origin |
| 202.28.168.0/24 | REACH | Invalid: origin |
| 202.28.169.0/24 | REACH | Invalid: origin |
| 202.28.170.0/24 | REACH | Invalid: origin |
| 202.28.171.0/24 | REACH | Invalid: origin |
| 202.28.172.0/24 | REACH | Invalid: origin |
| 202.28.173.0/24 | REACH | Invalid: origin |
| 202.28.174.0/24 | REACH | Invalid: origin |
| 202.28.175.0/24 | REACH | Invalid: origin |
| 202.28.176.0/21 | REACH | Invalid: origin |
| 202.28.176.0/24 | REACH | Invalid: origin |
| 202.28.177.0/24 | REACH | Invalid: origin |
| 202.28.178.0/24 | REACH | Invalid: origin |
| 202.28.179.0/24 | REACH | Invalid: origin |
| 202.28.180.0/24 | REACH | Invalid: origin |
| 202.28.181.0/24 | REACH | Invalid: origin |
| 202.28.182.0/24 | REACH | Invalid: origin |
| 202.28.183.0/24 | REACH | Invalid: origin |
| 202.28.184.0/21 | REACH | Invalid: origin |
| 202.28.244.0/22 | REACH | Invalid: origin |
| 202.28.245.0/24 | REACH | Invalid: origin |
| 202.28.246.0/24 | REACH | Invalid: origin |
| 202.28.247.0/24 | REACH | Invalid: origin |
| 202.28.248.0/22 | REACH | Invalid: origin |
| 202.28.249.0/24 | REACH | Invalid: origin |
| 202.28.250.0/24 | REACH | Invalid: origin |
| 202.28.251.0/24 | REACH | Invalid: origin |
| 202.41.160.0/24 | RADB, REACH | No ROA |
| 202.44.68.0/22 | RADB, REACH | No ROA |
| 202.90.112.0/22 | REACH | No ROA |
| 202.90.116.0/23 | REACH | No ROA |
| 202.90.118.0/24 | REACH | No ROA |
| 202.90.119.0/24 | REACH | No ROA |
| 202.90.120.0/22 | REACH | No ROA |
| 202.90.124.0/22 | REACH | No ROA |
| 202.91.20.0/24 | REACH | Invalid: origin |
| 202.91.21.0/24 | REACH | Invalid: origin |
| 202.91.22.0/24 | REACH | Invalid: origin |
| 202.91.23.0/24 | REACH | Invalid: origin |
| 203.146.205.0/24 | REACH | Invalid: origin |
| 203.146.253.0/24 | REACH | Invalid: origin |
| 203.148.136.0/23 | REACH | No ROA |
| 203.148.138.0/23 | REACH | No ROA |
| 203.148.144.0/20 | REACH | No ROA |
| 203.155.54.0/24 | REACH | Invalid: maxLength |
| 203.155.80.0/24 | REACH | Invalid: maxLength |
| 203.155.100.0/24 | REACH | Invalid: maxLength |
| 203.155.255.0/24 | APNIC, RADB | Valid |
| 203.159.32.0/19 | REACH | Invalid: origin |
| 203.170.161.0/24 | REACH | Invalid: origin |
| 203.170.172.0/24 | REACH | Invalid: origin |
| 203.170.173.0/24 | REACH | Invalid: origin |
| 203.170.174.0/24 | REACH | Invalid: origin |
| 203.170.190.0/24 | REACH | Invalid: origin |
| 203.188.0.0/21 | APNIC | Valid |
| 203.188.0.0/22 | APNIC | Valid |
| 203.188.0.0/23 | APNIC | Valid |
| 203.188.0.0/24 | APNIC, RADB | Valid |
| 203.188.2.0/23 | APNIC | Valid |
| 203.188.3.0/24 | APNIC, RADB | Valid |
| 203.188.4.0/22 | APNIC | Valid |
| 203.188.4.0/23 | APNIC | Valid |
| 203.188.6.0/23 | APNIC | Valid |
| 203.188.7.0/24 | APNIC | Valid |
| 203.188.8.0/21 | APNIC | Valid |
| 203.188.8.0/22 | APNIC | Valid |
| 203.188.8.0/23 | APNIC | Valid |
| 203.188.8.0/24 | APNIC | Valid |
| 203.188.9.0/24 | APNIC | Valid |
| 203.188.10.0/23 | APNIC | Valid |
| 203.188.11.0/24 | APNIC | Valid |
| 203.188.12.0/22 | APNIC | Valid |
| 203.188.13.0/24 | APNIC, RADB | Valid |
| 203.188.14.0/23 | APNIC | Valid |
| 203.188.14.0/24 | APNIC | Valid |
| 203.188.15.0/24 | APNIC | Valid |
| 203.188.16.0/20 | REACH | Invalid: maxLength |
| 203.188.32.0/21 | APNIC | Valid |
| 203.188.32.0/22 | APNIC | Valid |
| 203.188.32.0/23 | APNIC | Valid |
| 203.188.32.0/24 | APNIC | Valid |
| 203.188.33.0/24 | APNIC | Valid |
| 203.188.34.0/23 | APNIC | Valid |
| 203.188.34.0/24 | APNIC, RADB | Valid |
| 203.188.35.0/24 | APNIC | Valid |
| 203.188.36.0/22 | APNIC | Valid |
| 203.188.36.0/23 | APNIC | Valid |
| 203.188.36.0/24 | APNIC | Valid |
| 203.188.37.0/24 | APNIC | Valid |
| 203.188.38.0/23 | APNIC | Valid |
| 203.188.38.0/24 | APNIC | Valid |
| 203.188.39.0/24 | APNIC | Valid |
| 203.188.40.0/21 | APNIC | Valid |
| 203.188.40.0/22 | APNIC | Valid |
| 203.188.40.0/23 | APNIC | Valid |
| 203.188.40.0/24 | APNIC | Valid |
| 203.188.41.0/24 | APNIC | Valid |
| 203.188.42.0/23 | APNIC | Valid |
| 203.188.42.0/24 | APNIC | Valid |
| 203.188.43.0/24 | APNIC | Valid |
| 203.188.44.0/22 | APNIC | Valid |
| 203.188.44.0/23 | APNIC | Valid |
| 203.188.44.0/24 | APNIC | Valid |
| 203.188.45.0/24 | APNIC | Valid |
| 203.188.46.0/23 | APNIC | Valid |
| 203.188.46.0/24 | APNIC | Valid |
| 203.188.47.0/24 | APNIC | Valid |
| 203.188.48.0/20 | REACH | Invalid: maxLength |
| 203.209.0.0/17 | RADB | No ROA |
| 210.1.59.0/24 | REACH | Invalid: origin |
| 210.1.60.0/24 | REACH | Invalid: origin |
| 210.1.61.0/24 | REACH | Invalid: origin |
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.