Country
—
ASN LANDING PAGE
GWCOMMS-MPLS Gateway Communications
Last updated · Jul 20, 2026
Country
—
Total prefixes
265
IPv4 prefixes
265
IPv6 prefixes
0
GWCOMMS-MPLS Gateway Communications currently reports 265 prefixes and 42 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
GWCOMMS-MPLS Gateway Communications is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS37497
AS37497
—
AS37731
AS37731
—
AS33765
AS33765
—
AS20144
AS20144
—
AS30081
AS30081
—
AS36236
AS36236
—
AS6279
AS6279
—
AS20473
AS20473
—
AS198949
AS198949
—
AS7262
AS7262
—
AS24413
AS24413
—
AS19194
AS19194
—
AS23875
AS23875
—
AS55034
AS55034
—
AS59217
AS59217
—
AS16552
AS16552
—
AS48851
AS48851
—
AS36734
AS36734
—
AS327889
AS327889
—
AS4515
AS4515
—
AS328578
AS328578
—
AS63399
AS63399
—
AS19551
AS19551
—
AS328029
AS328029
—
AS3300
AS3300
—
AS37739
AS37739
—
AS36955
AS36955
—
AS4760
AS4760
—
AS10310
AS10310
—
AS12491
AS12491
—
AS29606
AS29606
—
AS33245
AS33245
—
AS40123
AS40123
—
AS42475
AS42475
—
AS45342
AS45342
—
AS55256
AS55256
—
AS328189
AS328189
—
AS328934
AS328934
—
AS329176
AS329176
—
AS329425
AS329425
—
| Prefix | Name | Country |
|---|---|---|
| 217.113.92.0/24 | AS31713 | — |
| 41.221.208.0/24 | AS31713 | — |
| 41.221.216.0/22 | AS31713 | — |
| 41.221.216.0/24 | AS31713 | — |
| 41.79.244.0/22 | AS31713 | — |
| 41.79.245.0/24 | AS31713 | — |
| 41.79.248.0/24 | AS31713 | — |
| 41.79.249.0/24 | AS31713 | — |
| 63.216.0.0/13 | AS31713 | — |
| 63.216.14.0/24 | AS31713 | — |
| 63.216.140.0/24 | AS31713 | — |
| 63.216.142.0/23 | AS31713 | — |
| 63.216.144.0/22 | AS31713 | — |
| 63.216.149.0/24 | AS31713 | — |
| 63.216.150.0/24 | AS31713 | — |
| 63.216.151.0/24 | AS31713 | — |
| 63.216.152.0/22 | AS31713 | — |
| 63.216.156.0/24 | AS31713 | — |
| 63.216.164.0/22 | AS31713 | — |
| 63.216.168.0/21 | AS31713 | — |
| 63.216.170.0/24 | AS31713 | — |
| 63.216.176.0/24 | AS31713 | — |
| 63.216.192.0/21 | AS31713 | — |
| 63.216.193.0/24 | AS31713 | — |
| 63.216.240.0/24 | AS31713 | — |
| 63.216.242.0/24 | AS31713 | — |
| 63.216.35.0/24 | AS31713 | — |
| 63.216.48.0/21 | AS31713 | — |
| 63.216.56.0/21 | AS31713 | — |
| 63.216.82.0/23 | AS31713 | — |
| 63.217.103.0/24 | AS31713 | — |
| 63.217.112.0/21 | AS31713 | — |
| 63.217.120.0/22 | AS31713 | — |
| 63.217.16.0/23 | AS31713 | — |
| 63.217.168.0/22 | AS31713 | — |
| 63.217.168.0/24 | AS31713 | — |
| 63.217.20.0/22 | AS31713 | — |
| 63.217.208.0/22 | AS31713 | — |
| 63.217.237.0/24 | AS31713 | — |
| 63.217.24.0/23 | AS31713 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS31713 is an autonomous system number. The current source associates it with GWCOMMS-MPLS Gateway Communications and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS31713. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS31713, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.