Skip to main content

AS218479

VDXNET

VDX Networks

Registry

Authoritative registration data

AS number
218479
Name
VDXNET
Organisation
VDX Networks
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

8

Total announced

11

Announced prefixes

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

Prefixes announced by AS218479
143.14.12.0/24 IPv4 /24 not checked
143.20.69.0/24 IPv4 /24 not checked
185.166.237.0/24 IPv4 /24 not checked
2001:678:1370::/48 IPv6 /48 RPKI valid
2a0d:f906:1::/48 IPv6 /48 not checked
2a0d:f906:2::/48 IPv6 /48 RPKI valid
2a0d:f906::/48 IPv6 /48 not checked
2a0f:85c1:c3b::/48 IPv6 /48 not checked
2a0f:85c1:db0::/48 IPv6 /48 RPKI not found
2a0f:85c1:db1::/48 IPv6 /48 RPKI not found
2a13:9500:46::/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 AS218479
Address families
LONAP: LON0 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 AS218479 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS218479 in AS paths

Observed upstreams
Families
AS61049 EXASCALE 439 1,350
v4 v6
AS6939 HURRICANE 217 1,214
v4 v6
AS8218 NEO-ASN 4 59
v4 v6
AS33891 CORE-BACKBONE 5 14
v4
AS39351 ESAB-AS 2 12
v4 v6
AS14840 ASN14840 2 10
v4
AS4455 BSO 2 6
v4
AS6204 ZET-NET 1 2
v4
AS9009 M247 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS218479 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 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.