Network · data from 2026-11-12
AS38713 Satcomm
Registry name: CONNECT2B-AS-PK - Broadband ISP, FTTH and Cable Service Provider, PK · PeeringDB
47IPv4 routes
76.6% RPKI valid · 95.7% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
11No ROA
2 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS38713, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38713, 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.
| 203.215.185.0/24 | No ROA | Other origin onlycovered by 203.215.184.0/23 | 673 100% |
| 203.215.184.0/24 | No ROA | Other origin onlycovered by 203.215.184.0/23 | 672 100% |
| 149.71.32.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.71.33.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.215.191.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 203.215.188.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 203.215.189.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 203.215.190.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 103.125.69.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.215.179.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.215.187.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.25.136.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.25.138.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.25.139.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.205.176.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.205.177.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.205.178.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.205.179.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 160.19.23.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.143.112.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.143.115.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.143.126.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.143.127.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.121.40.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.41.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.42.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.121.43.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.19.20.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.19.21.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.19.22.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.25.137.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 116.206.140.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 116.206.141.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 116.206.142.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 116.206.143.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 202.143.113.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.114.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 202.143.116.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.117.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.118.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.119.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.120.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.121.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.122.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.123.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.124.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 202.143.125.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2406:1300::/32 | Valid | RIR databaseAPNIC | 631 99% |
AS-SET
AS38713'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 26 are in fix.csv.
- ROA: none11
- Route object: none2
- Route object: RIR6
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.215.185.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: none | 203.215.185.0/24 | Route objects for it name AS17557, AS17787, AS38193. A route object for 203.215.184.0/23 with origin AS38713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38713 in the RIR database for the space. |
| ROA: none | 203.215.184.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: none | 203.215.184.0/24 | Route objects for it name AS17557, AS17787, AS38193. A route object for 203.215.184.0/23 with origin AS38713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38713 in the RIR database for the space. |
| ROA: none | 149.71.32.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 149.71.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.71.33.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 149.71.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.215.191.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 203.215.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.215.188.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 203.215.188.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.215.189.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 203.215.189.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.215.190.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| Route object: RIR | 203.215.190.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.125.69.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| ROA: none | 203.215.179.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
| ROA: none | 203.215.187.0/24 | No ROA covers it. Add a ROA for AS38713, maxLength 24. |
Route objects not announced
Route objects with origin AS38713 whose prefix no peer sees AS38713 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.25.136.0/22 | APNIC | Valid |
| 103.121.40.0/22 | APNIC | Valid |
| 103.205.176.0/22 | APNIC | Valid |
| 160.19.20.0/22 | APNIC | Valid |
| 202.143.112.0/20 | APNIC | Valid |
| 203.215.184.0/23 | APNIC | No ROA |
| 203.215.188.0/22 | APNIC | 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.