Network · data from 2026-11-12
AS63850 ENTRUSTICT-AS-AP - QRHUB PTY LTD T/A Entrust ICT
Registry name: ENTRUSTICT-AS-AP - QRHUB PTY LTD T/A Entrust ICT, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63850, 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.91.66.0/23 | No ROA | None | 671 100% |
| 203.91.64.0/21 | No ROA | None | 670 100% |
| 210.0.112.0/21 | No ROA | Other IRR onlyRADB | 670 100% |
| 124.246.7.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 124.246.16.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 124.246.18.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 124.246.19.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 124.246.21.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 124.246.22.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.44.170.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.30.197.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.34.109.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.91.65.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.91.67.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.91.68.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.91.69.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.91.70.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.91.71.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 124.246.0.0/21 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 124.246.4.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 124.246.16.0/21 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 124.246.17.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 124.246.20.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 124.246.23.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 138.252.168.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 203.91.64.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.91.66.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 210.0.112.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 210.0.113.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 210.0.115.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 210.0.116.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 138.252.168.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 210.0.114.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 138.252.169.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS63850 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 39 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced33
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.91.66.0/23 | No ROA covers it. Add a ROA for AS63850, maxLength 23. |
| Route object: none | 203.91.66.0/23 | No route object for it. Add a route object with origin AS63850 in the RIR database for the space. |
| ROA: none | 203.91.64.0/21 | No ROA covers it. Add a ROA for AS63850, maxLength 21. |
| Route object: none | 203.91.64.0/21 | No route object for it. Add a route object with origin AS63850 in the RIR database for the space. |
| ROA: none | 210.0.112.0/21 | No ROA covers it. Add a ROA for AS63850, maxLength 21. |
| Route object: RIR | 210.0.112.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63850 whose prefix no peer sees AS63850 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.100.119.0/29 | RADB | No ROA |
| 103.234.14.0/23 | APNIC | Valid |
| 103.234.14.0/24 | APNIC | Valid |
| 103.234.15.0/24 | APNIC | Valid |
| 202.44.175.88/29 | RADB | No ROA |
| 202.44.176.192/29 | RADB | No ROA |
| 202.44.176.208/29 | RADB | No ROA |
| 202.44.183.80/29 | RADB | No ROA |
| 202.44.184.112/29 | RADB | No ROA |
| 202.44.185.232/29 | RADB | No ROA |
| 202.44.190.96/29 | RADB | No ROA |
| 203.14.28.0/24 | RADB | No ROA |
| 203.15.104.0/24 | RADB | No ROA |
| 203.19.159.0/24 | RADB | No ROA |
| 203.55.171.0/24 | RADB | No ROA |
| 203.55.172.0/24 | RADB | No ROA |
| 203.91.64.0/23 | APNIC | Valid |
| 203.91.68.0/22 | APNIC | Valid |
| 210.0.65.128/29 | RADB | No ROA |
| 210.0.67.32/29 | RADB | No ROA |
| 210.0.73.64/29 | RADB | No ROA |
| 210.0.75.144/29 | RADB | No ROA |
| 210.0.76.40/29 | RADB | No ROA |
| 210.0.76.192/29 | RADB | No ROA |
| 210.0.78.24/29 | RADB | No ROA |
| 210.0.78.112/28 | RADB | No ROA |
| 210.0.84.96/27 | RADB | No ROA |
| 210.0.106.32/27 | RADB | No ROA |
| 210.0.112.0/22 | APNIC | Valid |
| 210.0.116.0/23 | APNIC | Valid |
| 210.0.118.0/24 | APNIC | Valid |
| 210.0.119.0/24 | APNIC | Valid |
| 210.0.124.8/29 | RADB | 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.