bgpreport

Network · data from 2026-11-12

AS214809 Stocade

Registry name: Stocade Jere Kiitola trading as Stocade, FI · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
3Route objects not announced registered with origin AS214809, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214809, 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.
103.139.88.0/24 Valid RIR databaseRIPE 673 100% 66
216.109.179.0/24 Valid RIR databaseARIN 668 99% 67
2a0a:6044:b300::/42 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS214809: AS214809:AS-ALL. 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 (AS214809 isn't in the set, or no route object for AS214809 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.

NameDatabaseASNsSets Route objectsAS214809 in itNot covered
AS214809:AS-ALL RIPE6 member sets in no database: AS-SERVOSPHERE, AS199746:AS-NEXTSERV, AS206604:AS-DOWNSTREAMS, AS214129:AS-GSTMNT, AS215110:AS-CUSTOMERS … 4311588,547 Yes 0

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 9 are in fix.csv.

  • AS-SET: missing member6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS-SERVOSPHERE; no IRR database read has it.
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS206604:AS-DOWNSTREAMS; no IRR database read has it.
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS214129:AS-GSTMNT; no IRR database read has it.
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS214809:AS-ALLAS214809:AS-ALL (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.

Route objects not announced

Route objects with origin AS214809 whose prefix no peer sees AS214809 announce. Many are kept on purpose (backup routes, space announced only in some places).

2602:f71e:ff::/48ARINValid
2a0a:6044:b300::/40RIPEValid
2a0f:85c1:807::/48RIPEValid

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.