AS31713 GWCOMMS-MPLS Gateway Communications
π§πͺOrg handle: ORG-CdCA1-RIPE
A PCCW Company
RIPE NCCallocated
Announced Prefixes (BGP)
263total
261 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)545,536
Announced (BGP)696,320
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)2.4Γ10Β²β΄
Prefix Limit (IPv4)
1,000
Prefix Limit (IPv6)
10
Country
π§πͺ BERIR
RIPE NCCStatus
allocated
Allocated
2004-07-23
Announced Prefixes
(BGP)263|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
41.79.244.0/22MOAS | Valid | - | 2026-10-11 |
41.79.245.0/24MOAS | Valid | - | 2026-10-11 |
41.79.248.0/24MOAS | Valid | - | 2026-10-11 |
41.79.249.0/24MOAS | Valid | - | 2026-10-11 |
41.221.208.0/24MOAS | Valid | - | 2026-10-11 |
41.221.216.0/22MOAS | Valid | - | 2026-10-11 |
41.221.216.0/24MOAS | Valid | - | 2026-10-11 |
63.216.0.0/13MOAS | Valid | APNIC | 2026-10-11 |
63.216.14.0/24MOAS | Valid | APNIC | 2026-10-11 |
63.216.35.0/24MOAS | Valid | APNIC | 2026-10-11 |
1-10 of 263
1 / 27
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 41.79.244.0/22 | π²πΏ MZ | AFRINIC | allocated |
| 41.79.245.0/24 | π²πΏ MZ | AFRINIC | assigned |
| 41.79.248.0/24 | πΏπ¦ ZA | AFRINIC | assigned |
| 41.221.208.0/24 | πΏπ¦ ZA | AFRINIC | assigned |
| 63.216.0.0/13 | ππ° HK | APNIC | allocated |
| 63.219.52.0/22 | πΊπΈ US | APNIC | assigned |
| 63.220.64.0/18 | πΊπΈ US | APNIC | assigned |
| 63.221.192.0/21 | πΊπΈ US | APNIC | assigned |
All 263 announced prefixes of AS31713 β
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS31713 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS31713 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS31713 in the transit part of AS paths: peers, providers or customers.
- AS3491PCCWG APAC HK PCCW Global HK7
ASPA
No ASPA
Abuse Contact
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 AS31713 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/31713Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31713" | jq