Skip to main content

AS218805

STACKLAYER-NET

<-------------------------------------------->

Registry

Authoritative registration data

AS number
218805
Name
STACKLAYER-NET
Organisation
<-------------------------------------------->
Country
—
RIR
RIPE
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 AS218805
185.67.22.0/24 IPv4 /24 not checked
222.167.221.0/24 IPv4 /24 not checked
2a0f:6282:5000::/36 IPv6 /36 RPKI valid
2a14:f705:c876::/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 AS218805
Address families
LONAP: LON0 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 AS218805 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS218805 in AS paths

Observed upstreams
Families
AS215638 AS-CILIX-LIMITED 519 901
v4 v6
AS6939 HURRICANE 368 732
v4 v6
AS212396 FYFEWEB 301 460
v4 v6
AS8218 NEO-ASN 7 47
v4 v6
AS39351 ESAB-AS 4 8
v4 v6
AS14840 ASN14840 2 5
v4
AS4455 BSO 2 3
v4 v6
AS9009 M247 2 2
v4 v6
AS6204 ZET-NET 1 1
v4
AS137409 GSLNETWORKS-AS-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS218805 in AS paths

Observed downstreams
Families
AS40419 282 498
v4 v6
AS218995 BMD3-AS 261 359
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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