Skip to main content

AS24586

NL-INTERMAX

Intermax Cloudsourcing B.V.

Registry

Authoritative registration data

AS number
24586
Name
NL-INTERMAX
Organisation
Intermax Cloudsourcing B.V.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

2

Total announced

19

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS24586
149.146.0.0/16 IPv4 /16 not checked
188.66.16.0/21 IPv4 /21 RPKI valid
46.22.184.0/21 IPv4 /21 RPKI valid
80.95.160.0/21 IPv4 /21 not checked
185.39.120.0/22 IPv4 /22 RPKI valid
194.13.104.0/22 IPv4 /22 not checked
46.22.180.0/22 IPv4 /22 RPKI valid
80.95.168.0/22 IPv4 /22 RPKI valid
80.95.172.0/22 IPv4 /22 RPKI valid
93.189.128.0/22 IPv4 /22 not checked
93.92.100.0/22 IPv4 /22 RPKI valid
93.92.96.0/22 IPv4 /22 RPKI valid
93.92.96.0/23 IPv4 /23 RPKI valid
149.146.3.0/24 IPv4 /24 not checked
46.22.181.0/24 IPv4 /24 not checked
46.22.183.0/24 IPv4 /24 not checked
93.92.103.0/24 IPv4 /24 not checked
2001:4c10::/32 IPv6 /32 not checked
2a00:f320::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS24586
Address families
AMS-IX 20,000 Mbps IPv4 · IPv6
NL-ix: Main 20,000 Mbps IPv4 · IPv6
R_iX: Main 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS24586 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

46 networks seen before AS24586 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS24586 in AS paths

Observed downstreams
Families
AS203318 asbizwaynl 381 1,430
v4 v6
AS61428 FOX 376 576
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

42 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.