AS398478 PEG-HK - PEG TECH INC
πΊπΈARINassigned
Announced Prefixes (BGP)
83total
83 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)169,472
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
200
Prefix Limit (IPv6)
5
Country
πΊπΈ USRIR
ARINStatus
assigned
Allocated
2020-06-18
Routing hygiene
Score 35/100 Β· Medium riskRPKI ROA coverage
45.9%
2 prefixes RPKI invalid
IRR route objects
97.6%
2 prefixes registered for another origin
Hijack signals
2
2 announced against others' ROAs, 0 own announced by others
Upstreams
5
diversity 72/100
- 54% of announced prefixes (46 of 85) have no valid ROA, 2 of them RPKI invalid
- Announces 2 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
Based on 85 announced prefixes, updated daily (2026-10-18). How the score works Β· RPKI explained
Announced Prefixes
(BGP)83|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | - | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 |
1-10 of 83
1 / 9
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 103.88.188.0/22 | ππ° HK | APNIC | allocated |
| 116.204.236.0/22 | ππ° HK | APNIC | allocated |
| 163.128.146.0/24 | ππ° HK | APNIC | assigned |
All 83 announced prefixes of AS398478 β
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS398478 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS398478 passes on: usually its customers.
- AS398993PEG TECH1
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS398478 should publish an ASPA object
- IPv4 transfers in the ARIN regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/398478Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/398478" | jq