Network · data from 2026-11-12
AS24187 KIRZ
Registry name: KIRZ-AS-TH - KIRZ Service Provider, TH · PeeringDB
86IPv4 routes
98.8% RPKI valid · 100.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
0 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
80Route objects not announced
registered with origin AS24187, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24187, 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.
| 38.58.186.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 2407:7a00::/32 | Valid | Other IRR onlyRADB | 634 100% |
| 27.131.146.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.109.60.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 202.173.217.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.173.218.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.173.219.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.173.220.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 27.131.128.0/18 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.129.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.130.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.133.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.134.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.135.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.136.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.138.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.144.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.145.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.154.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.160.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.165.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.167.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.173.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.179.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.180.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.181.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.183.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.189.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.191.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.109.60.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.109.61.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.109.62.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.109.63.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.173.208.0/20 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.131.128.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.131.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.132.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.137.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.139.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.140.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.141.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.142.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.143.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.147.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.148.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.149.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.150.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.151.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.152.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.153.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.155.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.156.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.157.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.158.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.161.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.162.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.163.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.164.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.166.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.168.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.169.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.170.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.171.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.174.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.175.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.176.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.177.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.178.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.182.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.184.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.185.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.186.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.187.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.188.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 27.131.190.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.208.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.209.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.210.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.211.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.212.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.213.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.214.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.215.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.216.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.221.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.222.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.173.223.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
AS-SET
AS24187'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 83 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced80
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.58.186.0/24 | No ROA covers it. Add a ROA for AS24187, maxLength 24. |
| Route object: RIR | 38.58.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2407:7a00::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24187 whose prefix no peer sees AS24187 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.131.128.0/19 | APNIC, RADB | Valid |
| 27.131.128.0/20 | APNIC | Valid |
| 27.131.128.0/21 | APNIC | Valid |
| 27.131.128.0/22 | APNIC | Valid |
| 27.131.128.0/23 | APNIC | Valid |
| 27.131.130.0/23 | APNIC | Valid |
| 27.131.132.0/22 | APNIC | Valid |
| 27.131.132.0/23 | APNIC | Valid |
| 27.131.134.0/23 | APNIC | Valid |
| 27.131.136.0/21 | APNIC | Valid |
| 27.131.136.0/22 | APNIC | Valid |
| 27.131.136.0/23 | APNIC | Valid |
| 27.131.138.0/23 | APNIC | Valid |
| 27.131.140.0/22 | APNIC | Valid |
| 27.131.140.0/23 | APNIC | Valid |
| 27.131.142.0/23 | APNIC | Valid |
| 27.131.144.0/20 | APNIC | Valid |
| 27.131.144.0/21 | APNIC | Valid |
| 27.131.144.0/22 | APNIC | Valid |
| 27.131.144.0/23 | APNIC | Valid |
| 27.131.146.0/23 | APNIC | Valid |
| 27.131.148.0/22 | APNIC | Valid |
| 27.131.148.0/23 | APNIC | Valid |
| 27.131.150.0/23 | APNIC | Valid |
| 27.131.152.0/21 | APNIC | Valid |
| 27.131.152.0/22 | APNIC | Valid |
| 27.131.152.0/23 | APNIC | Valid |
| 27.131.154.0/23 | APNIC | Valid |
| 27.131.156.0/22 | APNIC | Valid |
| 27.131.156.0/23 | APNIC | Valid |
| 27.131.158.0/23 | APNIC | Valid |
| 27.131.159.0/24 | APNIC | Valid |
| 27.131.160.0/19 | APNIC | Valid |
| 27.131.160.0/20 | APNIC | Valid |
| 27.131.160.0/21 | APNIC | Valid |
| 27.131.160.0/22 | APNIC | Valid |
| 27.131.160.0/23 | APNIC | Valid |
| 27.131.162.0/23 | APNIC | Valid |
| 27.131.164.0/22 | APNIC | Valid |
| 27.131.164.0/23 | APNIC | Valid |
| 27.131.166.0/23 | APNIC | Valid |
| 27.131.168.0/21 | APNIC | Valid |
| 27.131.168.0/22 | APNIC | Valid |
| 27.131.168.0/23 | APNIC | Valid |
| 27.131.170.0/23 | APNIC | Valid |
| 27.131.172.0/22 | APNIC | Valid |
| 27.131.172.0/23 | APNIC | Valid |
| 27.131.172.0/24 | APNIC | Valid |
| 27.131.174.0/23 | APNIC | Valid |
| 27.131.176.0/20 | APNIC | Valid |
| 27.131.176.0/21 | APNIC | Valid |
| 27.131.176.0/22 | APNIC | Valid |
| 27.131.176.0/23 | APNIC | Valid |
| 27.131.178.0/23 | APNIC | Valid |
| 27.131.180.0/22 | APNIC | Valid |
| 27.131.180.0/23 | APNIC | Valid |
| 27.131.182.0/23 | APNIC | Valid |
| 27.131.184.0/21 | APNIC | Valid |
| 27.131.184.0/22 | APNIC | Valid |
| 27.131.184.0/23 | APNIC | Valid |
| 27.131.186.0/23 | APNIC | Valid |
| 27.131.188.0/22 | APNIC | Valid |
| 27.131.188.0/23 | APNIC | Valid |
| 27.131.190.0/23 | APNIC | Valid |
| 103.109.60.0/23 | APNIC | Valid |
| 103.109.62.0/23 | APNIC | Valid |
| 202.173.208.0/21 | APNIC | Valid |
| 202.173.208.0/22 | APNIC | Valid |
| 202.173.208.0/23 | APNIC | Valid |
| 202.173.210.0/23 | APNIC | Valid |
| 202.173.212.0/22 | APNIC | Valid |
| 202.173.212.0/23 | APNIC | Valid |
| 202.173.214.0/23 | APNIC | Valid |
| 202.173.216.0/21 | APNIC | Valid |
| 202.173.216.0/22 | APNIC | Valid |
| 202.173.216.0/23 | APNIC | Valid |
| 202.173.218.0/23 | APNIC | Valid |
| 202.173.220.0/22 | APNIC | Valid |
| 202.173.220.0/23 | APNIC | Valid |
| 202.173.222.0/23 | APNIC | 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.