Country
—
ASN LANDING PAGE
ERANIUM Eranium B.V.
Last updated · Apr 10, 2026
Country
—
Total prefixes
6
IPv4 prefixes
3
IPv6 prefixes
3
ERANIUM Eranium B.V. currently shows 6 prefixes and 71 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.
ERANIUM Eranium B.V. 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.
AS50917
AS50917
—
AS35661
AS35661
—
AS34872
AS34872
—
AS212895
AS212895
—
AS52025
AS52025
—
AS149020
AS149020
—
AS58061
AS58061
—
AS208453
AS208453
—
AS57706
AS57706
—
AS46824
AS46824
—
AS210558
AS210558
—
AS212253
AS212253
—
AS136258
AS136258
—
AS51396
AS51396
—
AS212762
AS212762
—
AS1002
AS1002
—
AS215085
AS215085
—
AS400799
AS400799
—
AS211588
AS211588
—
AS214809
AS214809
—
AS44733
AS44733
—
AS207994
AS207994
—
AS44299
AS44299
—
AS401988
AS401988
—
AS49033
AS49033
—
AS201949
AS201949
—
AS211041
AS211041
—
AS400587
AS400587
—
AS200223
AS200223
—
AS931
AS931
—
AS39563
AS39563
—
AS44103
AS44103
—
AS206272
AS206272
—
AS202956
AS202956
—
AS213527
AS213527
—
AS209267
AS209267
—
AS213842
AS213842
—
AS64404
AS64404
—
AS60150
AS60150
—
AS51198
AS51198
—
AS1299
AS1299
—
AS6830
AS6830
—
AS3356
AS3356
—
AS6453
AS6453
—
AS174
AS174
—
AS3257
AS3257
—
AS6762
AS6762
—
AS6939
AS6939
—
AS5511
AS5511
—
AS34927
AS34927
—
AS24482
AS24482
—
AS50304
AS50304
—
AS199524
AS199524
—
AS20764
AS20764
—
AS8283
AS8283
—
AS12859
AS12859
—
AS50629
AS50629
—
AS286
AS286
—
AS205112
AS205112
—
AS24961
AS24961
—
AS28917
AS28917
—
AS41327
AS41327
—
AS39122
AS39122
—
AS271253
AS271253
—
AS56655
AS56655
—
AS209823
AS209823
—
AS263152
AS263152
—
AS34872
AS34872
—
AS1031
AS1031
—
AS6204
AS6204
—
AS50917
AS50917
—
| Prefix | Name | Country |
|---|---|---|
| 217.18.95.0/24 | AS35133 | — |
| 2a07:5500::/29 | AS35133 | — |
| 2a09:e240:22::/48 | AS35133 | — |
| 2a09:e244::/33 | AS35133 | — |
| 45.13.117.0/24 | AS35133 | — |
| 77.73.114.0/24 | AS35133 | — |
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.
AS35133 is an autonomous system number used to identify an independently operated network. The current page associates it with ERANIUM Eranium B.V. 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 AS35133. 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 AS35133, 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.