AS72Schlumberger Limited
As of 23rd October 2026, AS72 (Schlumberger Limited), a network registered in the United States with ARIN, originates 138 IPv4 prefixes covering 1.3M addresses. By IPv4 address space that makes it the 395th-largest of the 79,658 networks we see originating IPv4, and the 94th-largest of 18,483 in the United States. It is seen behind 37 upstream networks, most often AS6939 (Hurricane Electric LLC) and AS174 (Cogent Communications, LLC). 1% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. Over 99% of its routes reach at least 90% of full-feed peers, and 2 prefixes are also originated by another network.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS72 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS72 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
78
adjacent networks
- Upstreams
- 3747%
- Peers
- 4153%
- Downstreams
- 00%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS6939Hurricane Electric LLC | Peer | 6,342 | 75 | |
| AS174Cogent Communications, LLC | Peer | 737 | 14 | |
| AS1273Vodafone Group PLC | Peer | 528 | 77 | |
| AS3300British Telecommunications Limited | Peer | 385 | 77 | |
| AS6660Vodafone Enterprise Equipment Limited | Peer | 325 | 61 | |
| AS5400British Telecommunications (International) | Peer | 308 | 77 | |
| AS8359MTS PJSC | Peer | 161 | 64 | |
| AS35104QMOBILE JSC | Peer | 154 | 77 | |
| AS24785Joint Transit (Broadband Hosting B.V.) | Peer | 133 | 7 | |
| AS3216Vimpelcom PJSC | Peer | 117 | 59 |
Prefixes
All 138The largest blocks AS72 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 128.58.0.0/16 | 65.5k | 77/77 |
| 129.87.0.0/16 | 65.5k | 77/77 |
| 134.32.0.0/16 | 65.5k | 77/77 |
| 136.249.0.0/16 | 65.5k | 77/77 |
| 136.250.0.0/16 | 65.5k | 77/77 |
| 136.251.0.0/16 | 65.5k | 77/77 |
| 136.252.0.0/16 | 65.5k | 77/77 |
| 136.253.0.0/16 | 65.5k | 77/77 |
| 136.254.0.0/16 | 65.5k | 77/77 |
| 137.144.0.0/16 | 65.5k | 77/77 |
Routing health
How AS72's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid1.4%2
- Invalid0.0%0
- No ROA98.6%136
Propagation
- Globally propagated90% of full-feed peers or more99.3%137
- Partially propagated40% to 90%0.7%1
- Seen by few peersUnder 40%0.0%0
Prefix sizes
Recent changes
Announcements that started or stopped since 24th Sept 2026.
No announcement by AS72 started or stopped in this period.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.