Skip to main content

AS216096

SECUREPEAK

============================================================

Registry

Authoritative registration data

AS number
216096
Name
SECUREPEAK
Organisation
============================================================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

3

Total announced

7

Announced prefixes

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

Prefixes announced by AS216096
109.175.210.0/24 IPv4 /24 not checked
109.205.193.0/24 IPv4 /24 not checked
158.94.220.0/24 IPv4 /24 not checked
158.94.221.0/24 IPv4 /24 not checked
2a01:fb01::/32 IPv6 /32 not checked
2a01:fb04::/32 IPv6 /32 not checked
2a01:fb06::/32 IPv6 /32 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 AS216096
Address families
BGP.Exchange - Amsterdam 1,000 Mbps IPv6
BGP.Exchange - Dusseldorf 1,000 Mbps IPv6
BGP.Exchange - Frankfurt 1,000 Mbps IPv6
BGP.Exchange - London 1,000 Mbps IPv6
BGP.Exchange - Zurich 1,000 Mbps IPv6
ERA-IX Amsterdam 20,000 Mbps IPv4 · IPv6
FREMIX 2,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
GNM-IX 10,000 Mbps IPv4 · IPv6
IX Australia Adelaide (SA-IX): SA-IX 10,000 Mbps IPv4 · IPv6
IX Australia Brisbane (QLD-IX): QLD-IX 10,000 Mbps IPv4 · IPv6
IX Australia Melbourne (VIC-IX): VIC-IX 10,000 Mbps IPv4 · IPv6
IX Australia Sydney (NSW-IX): NSW-IX 10,000 Mbps IPv4 · IPv6
KCIX 100,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
LINX LON1: Main 4,000 Mbps IPv4 · IPv6
LINX LON2 4,000 Mbps IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX NETHERLANDS: Peering LAN 1,000 Mbps IPv4 · IPv6
LONAP: LON0 5,000 Mbps IPv4 · IPv6
NL-ix: Main 10,000 Mbps IPv4 · IPv6
NVIX 1,000 Mbps IPv4 · IPv6
ONIX 1,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 10,000 Mbps IPv4 · IPv6
TurkIX Sofia 100,000 Mbps IPv4 · IPv6
nine 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 AS216096 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

37 networks seen before AS216096 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS216096 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

47 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 21
v4 v6
AS24482 SGGS-AS-AP 1 12
v4 v6
AS48185 1 9
v4 v6
AS8529 OMANTEL-AS 1 8
v4 v6
AS62167 1 8
v4 v6
AS12859 1 7
v4 v6
AS14907 WIKIMEDIA 1 6
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS212483 level86 1 6
v4 v6
AS2027 1 4
v4 v6
AS3399 1 4
v4 v6
AS8298 1 4
v4 v6
AS16347 1 4
v4 v6
AS35600 1 4
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS39122 1 4
v4 v6
AS44097 1 4
v4 v6
AS49434 1 4
v4 v6
AS51185 MAINSTREAMING-AS 1 4
v4 v6
AS56987 AS-ABACLOUDA 1 4
v4 v6
AS58299 OPENFACTORY-AS 1 4
v4 v6
AS204092 1 4
v4 v6
AS209823 1 4
v4 v6
AS215628 1 4
v4 v6
AS1103 SURFNET-NL 1 3
v4 v6
AS1140 1 3
v4 v6
AS3212 1 3
v4 v6
AS3333 1 3
v4 v6
AS20932 1 3
v4 v6
AS29075 1 3
v4 v6
AS41666 1 3
v4 v6
AS42541 1 3
v4 v6
AS56662 1 3
v6
AS64475 1 3
v4 v6
AS205112 PHILUNET 1 3
v4 v6
AS212635 1 3
v6
AS17639 CONVERGE-AS 1 2
v6
AS45489 SLT-GLOBAL 1 2
v6
AS50629 LWLCOM 1 2
v6
AS50673 1 2
v6
AS29049 1 1
v4
AS34800 1 1
v6
AS37721 ORG-VTS1-AFRINIC 1 1
v4
AS198150 1 1
v4
AS199524 GCORE 1 1
v4
AS263152 1 1
v4
AS271253 1 1
v4

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.