Network · data from 2026-11-12

AS218805 STACKLAYER-NET

Registry name: STACKLAYER-NET Stacklayer Communications Limited, GB · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS218805, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS218805, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


185.67.22.0/24	Valid	RIR databaseRIPE	673 100%	66
222.167.221.0/24	Valid	RIR databaseRIPE	673 100%	67
2a14:f705:c876::/48	Valid	RIR databaseRIPE	635 100%	69
2a0f:6282:5000::/36	Valid	RIR databaseRIPE	634 100%	69

AS-SET

PeeringDB's irr_as_set for AS218805: RIPE::AS218805:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS218805 isn't in the set, or no route object for AS218805 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS218805 in it	Not covered
RIPE::AS218805:AS-CUSTOMERS	RIPE5 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-SERV, AS-STEFAN, AS152135:AS-CSSI, AS199746:AS-NEXTSERV	145	36	1,684	Yes	0

Name

Database

ASNs

Sets

Route objects

AS218805 in it

Not covered

RIPE::AS218805:AS-CUSTOMERS

RIPE5 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-SERV, AS-STEFAN, AS152135:AS-CSSI, AS199746:AS-NEXTSERV

145

1,684

Yes

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

AS-SET: missing member5

Change	Prefix or set	Detail
AS-SET: missing member	RIPE::AS218805:AS-CUSTOMERS	AS218805:AS-CUSTOMERS (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it.
AS-SET: missing member	RIPE::AS218805:AS-CUSTOMERS	AS218805:AS-CUSTOMERS (RIPE) lists AS-SERV; no IRR database read has it.
AS-SET: missing member	RIPE::AS218805:AS-CUSTOMERS	AS218805:AS-CUSTOMERS (RIPE) lists AS-STEFAN; no IRR database read has it.
AS-SET: missing member	RIPE::AS218805:AS-CUSTOMERS	AS218805:AS-CUSTOMERS (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing member	RIPE::AS218805:AS-CUSTOMERS	AS218805:AS-CUSTOMERS (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

RIPE::AS218805:AS-CUSTOMERS

AS218805:AS-CUSTOMERS (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it.

AS-SET: missing member

RIPE::AS218805:AS-CUSTOMERS

AS218805:AS-CUSTOMERS (RIPE) lists AS-SERV; no IRR database read has it.

AS-SET: missing member

RIPE::AS218805:AS-CUSTOMERS

AS218805:AS-CUSTOMERS (RIPE) lists AS-STEFAN; no IRR database read has it.

AS-SET: missing member

RIPE::AS218805:AS-CUSTOMERS

AS218805:AS-CUSTOMERS (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.

AS-SET: missing member

RIPE::AS218805:AS-CUSTOMERS

AS218805:AS-CUSTOMERS (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

Every route object with origin AS218805 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.