Country
—
ASN LANDING PAGE
SCHLUMBERGER-AS - Schlumberger Limited
Last updated · Apr 4, 2026
Country
—
Total prefixes
141
IPv4 prefixes
141
IPv6 prefixes
0
SCHLUMBERGER-AS - Schlumberger Limited currently shows 141 prefixes and 38 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
SCHLUMBERGER-AS - Schlumberger Limited is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
Detailed data for this ASN is not available right now.
AS151506
AS151506
—
AS3216
AS3216
—
AS35104
AS35104
—
AS6939
AS6939
—
AS6660
AS6660
—
AS1273
AS1273
—
AS9930
AS9930
—
AS8902
AS8902
—
AS52320
AS52320
—
AS55410
AS55410
—
AS2856
AS2856
—
AS135523
AS135523
—
AS18101
AS18101
—
AS196925
AS196925
—
AS15802
AS15802
—
AS8452
AS8452
—
AS8896
AS8896
—
AS8359
AS8359
—
AS5400
AS5400
—
AS3300
AS3300
—
AS3356
AS3356
—
AS16735
AS16735
—
AS9931
AS9931
—
AS8220
AS8220
—
AS25019
AS25019
—
AS2686
AS2686
—
AS35753
AS35753
—
AS12389
AS12389
—
AS132280
AS132280
—
AS9049
AS9049
—
AS174
AS174
—
AS2688
AS2688
—
AS20562
AS20562
—
AS24785
AS24785
—
AS4755
AS4755
—
AS24482
AS24482
—
AS49544
AS49544
—
AS199524
AS199524
—
| Prefix | Name | Country |
|---|---|---|
| 128.58.0.0/16 | AS72 | — |
| 129.87.0.0/16 | AS72 | — |
| 134.32.0.0/16 | AS72 | — |
| 136.249.0.0/16 | AS72 | — |
| 136.249.32.0/19 | AS72 | — |
| 136.249.64.0/18 | AS72 | — |
| 136.250.0.0/16 | AS72 | — |
| 136.251.0.0/16 | AS72 | — |
| 136.252.0.0/16 | AS72 | — |
| 136.252.128.0/17 | AS72 | — |
| 136.252.251.0/24 | AS72 | — |
| 136.252.252.0/24 | AS72 | — |
| 136.252.253.0/24 | AS72 | — |
| 136.252.254.0/24 | AS72 | — |
| 136.253.0.0/16 | AS72 | — |
| 136.253.192.0/18 | AS72 | — |
| 136.254.0.0/16 | AS72 | — |
| 137.144.0.0/16 | AS72 | — |
| 163.183.0.0/16 | AS72 | — |
| 163.184.0.0/16 | AS72 | — |
| 163.185.0.0/16 | AS72 | — |
| 163.186.0.0/16 | AS72 | — |
| 163.187.0.0/16 | AS72 | — |
| 163.188.0.0/16 | AS72 | — |
| 192.12.34.0/23 | AS72 | — |
| 192.12.40.0/24 | AS72 | — |
| 192.12.43.0/24 | AS72 | — |
| 192.23.0.0/16 | AS72 | — |
| 192.23.10.0/24 | AS72 | — |
| 192.23.100.0/24 | AS72 | — |
| 192.23.103.0/24 | AS72 | — |
| 192.23.104.0/24 | AS72 | — |
| 192.23.105.0/24 | AS72 | — |
| 192.23.108.0/24 | AS72 | — |
| 192.23.109.0/24 | AS72 | — |
| 192.23.11.0/24 | AS72 | — |
| 192.23.110.0/24 | AS72 | — |
| 192.23.119.0/24 | AS72 | — |
| 192.23.12.0/24 | AS72 | — |
| 192.23.127.0/24 | AS72 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS72 is an autonomous system number used to identify an independently operated network. The current page associates it with SCHLUMBERGER-AS - Schlumberger Limited in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS72. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS72, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.