Routing security
AS10133 Chief Telecom Inc.
Unclassified APNIC Route Server
Announcements
What this network originates
Every prefix observed with AS10133 as its origin, checked against RPKI and the IRR. Problems sort first.
No announcements from this network were observed in the routing snapshot.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS10133 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 160.30.78.0/23 | /32 | APNIC |
| 203.163.222.0/23 | /24 | APNIC |
| 2406:d400::/32 | /32 | APNIC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS10133 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 203.163.216.0/22 | RADB | Registered Route | MAINT-AS17408 | 2023-11-13 | Not announced |
| 203.163.216.0/23 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.217.0/24 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.218.0/23 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.218.0/24 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.219.0/24 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.222.0/23 | APNIC | Chief Telecom Inc. | MAINT-TW-CHIEF | 2018-06-22 | Not announced |
| 203.163.222.0/23 | RADB | Registered Route | MAINT-AS17408 | 2023-11-13 | Not announced |
| 203.163.222.0/24 | APNIC | Chief Telecom Inc. | MAINT-TW-CHIEF | 2018-06-22 | Not announced |
| 203.163.222.0/24 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 203.163.223.0/24 | APNIC | Chief Telecom Inc. | MAINT-TW-CHIEF | 2018-06-22 | Not announced |
| 203.163.223.0/24 | RADB | Proxy-registered route object | MAINT-HGC-INTL | 2026-10-02 | Not announced |
| 2406:d400::/32 | APNIC | Chief Telecom Inc. | MAINT-TW-UNIGATE | 2018-06-22 | Not announced |
| 2406:d400::/32 | RADB | Registered Route | MAINT-AS17408 | 2023-11-13 | Not announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS10133 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-TPIX | PeeringDB | Declared by the operator as its own set |
AS-ABOVE-AS-AP | RADB | Lists AS10133 as a direct member |
AS-CATONETWORKS | RIPE | Lists AS10133 as a direct member |
AS-HINET | RADB | Lists AS10133 as a direct member |
AS-UNIGATE-TRANSIT | RADB | Lists AS10133 as a direct member |
AS152610:AS-DIGIWOKER | APNIC | Lists AS10133 as a direct member |
AS18424:AS-IXP | RADB | Lists AS10133 as a direct member |
AS18424:AS-PEERS | RADB | Lists AS10133 as a direct member |
AS214575:AS-IXP | RIPE | Lists AS10133 as a direct member |
AS44324:AS-IXP | RIPE | Lists AS10133 as a direct member |
AS58453:AS-ASIAASCUST | APNIC | Lists AS10133 as a direct member |
AS58453:AS-ASIAASCUST | RADB | Lists AS10133 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.