AS54600 PEG-SV - PEG TECH INC
🇺🇸ARINassigned
Announced Prefixes (BGP)
647total
644 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)55,040
Announced (BGP)706,816
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)3.6×10²⁴
Routing hygiene
Score 58/100 · High riskRPKI ROA coverage
6.1%
39 prefixes RPKI invalid
IRR route objects
90.2%
59 prefixes registered for another origin
Hijack signals
33
32 announced against others' ROAs, 1 own announced by others
Upstreams
7
diversity 68/100
- 94% of announced prefixes (604 of 643) have no valid ROA, 39 of them RPKI invalid
- Announces 32 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- 8 prefixes registered in IRR route objects for another active network and not authorized by a ROA
Based on 643 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)647|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | - | |
| No ROA | Other IRR | - | |
| No ROA | - | - | |
| No ROA | - | - | |
| No ROA | Other IRR | - | |
| No ROA | - | - | |
| No ROA | Other IRR | - | |
| No ROA | Other IRR | - | |
| No ROA | - | - | |
| No ROA | - | - |
1-10 of 647
1 / 65
Allocated Prefixes
(RIR)20Prefix | Country | RIR | Status |
|---|---|---|---|
| 103.104.172.0/22 | 🇭🇰 HK | APNIC | assigned |
| 103.116.20.0/22 | 🇭🇰 HK | APNIC | allocated |
| 103.124.192.0/22 | 🇭🇰 HK | APNIC | allocated |
| 103.142.36.0/23 | 🇭🇰 HK | APNIC | allocated |
| 103.145.104.0/23 | 🇭🇰 HK | APNIC | allocated |
| 130.51.112.0/22 | 🇺🇸 US | ARIN | allocated |
| 142.0.128.0/20 | 🇺🇸 US | ARIN | allocated |
| 142.4.96.0/19 | 🇺🇸 US | ARIN | allocated |
| 192.74.224.0/19 | 🇺🇸 US | ARIN | allocated |
| 198.2.192.0/18 | 🇺🇸 US | ARIN | allocated |
1-10 of 20
1 / 2
All 647 announced prefixes of AS54600 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS54600 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS54600 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/54600Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/54600" | jq