Country
—
ASN LANDING PAGE
ITNSGLOBAL-AS ITNS GLOBAL EOOD
Last updated · Jul 20, 2026
Country
—
Total prefixes
63
IPv4 prefixes
8
IPv6 prefixes
55
ITNSGLOBAL-AS ITNS GLOBAL EOOD currently reports 63 prefixes and 40 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.
ITNSGLOBAL-AS ITNS GLOBAL EOOD 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.
AS57344
AS57344
—
AS6762
AS6762
—
AS3356
AS3356
—
AS6939
AS6939
—
AS33891
AS33891
—
AS5405
AS5405
—
AS25091
AS25091
—
AS8218
AS8218
—
AS50629
AS50629
—
AS39351
AS39351
—
AS41327
AS41327
—
AS49434
AS49434
—
AS50673
AS50673
—
AS400687
AS400687
—
AS137409
AS137409
—
AS208972
AS208972
—
AS3170
AS3170
—
AS6204
AS6204
—
AS8280
AS8280
—
AS9198
AS9198
—
AS13004
AS13004
—
AS15958
AS15958
—
AS24482
AS24482
—
AS28910
AS28910
—
AS35598
AS35598
—
AS37721
AS37721
—
AS44901
AS44901
—
AS48678
AS48678
—
AS49544
AS49544
—
AS49673
AS49673
—
AS51185
AS51185
—
AS56655
AS56655
—
AS56911
AS56911
—
AS62000
AS62000
—
AS205112
AS205112
—
AS209823
AS209823
—
AS21215
AS21215
—
AS60171
AS60171
—
| Prefix | Name | Country |
|---|---|---|
| 185.118.241.0/24 | AS31293 | — |
| 185.118.242.0/24 | AS31293 | — |
| 185.118.243.0/24 | AS31293 | — |
| 194.150.116.0/22 | AS31293 | — |
| 194.150.116.0/24 | AS31293 | — |
| 194.150.117.0/24 | AS31293 | — |
| 194.150.118.0/24 | AS31293 | — |
| 194.150.119.0/24 | AS31293 | — |
| 2a06:9680:10::/48 | AS31293 | — |
| 2a06:9680:11::/48 | AS31293 | — |
| 2a06:9680:12::/48 | AS31293 | — |
| 2a06:9680:13::/48 | AS31293 | — |
| 2a06:9680:14::/48 | AS31293 | — |
| 2a06:9680:15::/48 | AS31293 | — |
| 2a06:9680:16::/48 | AS31293 | — |
| 2a06:9680:17::/48 | AS31293 | — |
| 2a06:9680:18::/48 | AS31293 | — |
| 2a06:9680:1::/48 | AS31293 | — |
| 2a06:9680:1b::/48 | AS31293 | — |
| 2a06:9680:1c::/48 | AS31293 | — |
| 2a06:9680:1d::/48 | AS31293 | — |
| 2a06:9680:1e::/48 | AS31293 | — |
| 2a06:9680:1f::/48 | AS31293 | — |
| 2a06:9680:2::/48 | AS31293 | — |
| 2a06:9680:30::/48 | AS31293 | — |
| 2a06:9680:31::/48 | AS31293 | — |
| 2a06:9680:32::/48 | AS31293 | — |
| 2a06:9680:33::/48 | AS31293 | — |
| 2a06:9680:34::/48 | AS31293 | — |
| 2a06:9680:35::/48 | AS31293 | — |
| 2a06:9680:36::/48 | AS31293 | — |
| 2a06:9680:37::/48 | AS31293 | — |
| 2a06:9680:38::/48 | AS31293 | — |
| 2a06:9680:39::/48 | AS31293 | — |
| 2a06:9680:3::/48 | AS31293 | — |
| 2a06:9680:3a::/48 | AS31293 | — |
| 2a06:9680:3b::/48 | AS31293 | — |
| 2a06:9680:3c::/48 | AS31293 | — |
| 2a06:9680:3d::/48 | AS31293 | — |
| 2a06:9680:3e::/48 | AS31293 | — |
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.
AS31293 is an autonomous system number. The current source associates it with ITNSGLOBAL-AS ITNS GLOBAL EOOD 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 AS31293. 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 AS31293, 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.