Skip to main content

AS395915

ENS

Edge Network Services LLC

Registry

Authoritative registration data

AS number
395915
Name
ENS
Organisation
Edge Network Services LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS395915
130.12.255.0/24 IPv4 /24 not checked
207.2.127.0/24 IPv4 /24 not checked
2602:811:4000::/44 IPv6 /44 not checked
2602:811:4001::/48 IPv6 /48 not checked

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 AS395915
Address families
FCIX 10,000 Mbps IPv4 · IPv6
FREMIX 10,000 Mbps IPv4 · IPv6
Lambda-IX 10,000 Mbps IPv4 · IPv6
SBIX FRE 1,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 AS395915 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS395915 in AS paths

Observed upstreams
Families
AS400587 RYAMER 681 1,584
v4 v6
AS6939 HURRICANE 349 812
v4 v6
AS58057 SECUREBIT 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS395915 in AS paths

Observed downstreams
Families
AS19529 636 1,226
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 3
v4 v6

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.