bgpreport

Network · data from 2026-11-12

AS16302 SuomiCommunications

Registry name: SUOMICOMMUNICATIONS Suomi Communications Oy, FI · PeeringDB

14IPv4 routes 64.3% RPKI valid · 100.0% with a route object
3IPv6 routes 33.3% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS16302, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16302, 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.
193.138.126.0/24 No ROA RIR databaseRIPE 672 100% 66
193.142.251.0/24 No ROA RIR databaseRIPE 672 100% 66
193.161.205.0/24 No ROA RIR databaseRIPE 672 100% 66
194.110.23.0/24 No ROA RIR databaseRIPE 672 100% 66
194.116.231.0/24 No ROA RIR databaseRIPE 672 100% 66
2001:67c:2d6c::/48 No ROA RIR databaseRIPE 634 100% 67
2a02:e900::/32 No ROA RIR databaseRIPE 634 100% 67
77.246.192.0/20 Valid RIR databaseRIPE 672 100% 66
79.134.96.0/19 Valid RIR databaseRIPE 672 100% 66
80.248.240.0/20 Valid RIR databaseRIPE 672 100% 66
83.142.72.0/21 Valid RIR databaseRIPE 672 100% 66
185.9.8.0/22 Valid RIR databaseRIPE 672 100% 66
185.163.14.0/23 Valid RIR databaseRIPE 672 100% 66
188.127.192.0/19 Valid RIR databaseRIPE 672 100% 66
193.105.96.0/24 Valid RIR databaseRIPE 672 100% 66
217.119.32.0/20 Valid RIR databaseRIPE 672 100% 66
2a00:1190::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS16302: RIPE::AS-SUOMICOM. 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 (AS16302 isn't in the set, or no route object for AS16302 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 objectsAS16302 in itNot covered
RIPE::AS-SUOMICOM RIPE1 member set in no database: AS209186:AS-DOWNSTREAM 140136,990 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 8 are in fix.csv.

  • ROA: none7
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: none193.138.126.0/24No ROA covers it. Add a ROA for AS16302, maxLength 24.672 of 673
ROA: none193.142.251.0/24No ROA covers it. Add a ROA for AS16302, maxLength 24.672 of 673
ROA: none193.161.205.0/24No ROA covers it. Add a ROA for AS16302, maxLength 24.672 of 673
ROA: none194.110.23.0/24No ROA covers it. Add a ROA for AS16302, maxLength 24.672 of 673
ROA: none194.116.231.0/24No ROA covers it. Add a ROA for AS16302, maxLength 24.672 of 673
ROA: none2001:67c:2d6c::/48No ROA covers it. Add a ROA for AS16302, maxLength 48.634 of 636
ROA: none2a02:e900::/32No ROA covers it. Add a ROA for AS16302, maxLength 32.634 of 636
AS-SET: missing memberRIPE::AS-SUOMICOMAS-SUOMICOM (RIPE) lists AS209186:AS-DOWNSTREAM; no IRR database read has it.

Route objects not announced

Every route object with origin AS16302 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.