bgpreport

Network · data from 2026-11-12

AS13170 Kaisanet Oy

Registry name: KPO-AS Kaisanet Oy, FI · PeeringDB

11IPv4 routes 81.8% RPKI valid · 81.8% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 1 origin · 1 maxLength
0No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS13170, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13170, 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.
213.255.164.0/24 Invalid: origin None 2 0%low visibility 2
212.116.32.228/32 Invalid: maxLength Nonecovered by 212.116.32.0/19 0 0%low visibility 2
46.254.96.0/21 Valid RIR databaseRIPE 671 100% 67
62.145.160.0/19 Valid RIR databaseRIPE 671 100% 67
77.223.32.0/19 Valid RIR databaseRIPE 671 100% 67
85.29.64.0/18 Valid RIR databaseRIPE 671 100% 67
212.116.32.0/19 Valid RIR databaseRIPE 671 100% 67
213.143.160.0/19 Valid RIR databaseRIPE 671 100% 67
213.145.192.0/19 Valid RIR databaseRIPE 671 100% 67
185.69.36.0/22 Valid RIR databaseRIPE 669 99% 67
185.69.72.0/22 Valid RIR databaseRIPE 669 99% 67
2a04:25c0::/29 Valid RIR databaseRIPE 635 100% 67
2a05:1f40::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS13170: RIPE::AS-KAISANET. 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 (AS13170 isn't in the set, or no route object for AS13170 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 objectsAS13170 in itNot covered
RIPE::AS-KAISANET RIPE 5283 Yes 2

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

  • ROA: origin1
  • ROA: maxLength1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin213.255.164.0/24ROAs covering it name AS29240, not AS13170. If AS13170 should announce it, add a ROA for AS13170.2 of 673
Route object: none213.255.164.0/24No route object for it. Add a route object with origin AS13170 in the RIR database for the space.2 of 673
ROA: maxLength212.116.32.228/32ROA 212.116.32.0/19 AS13170 has maxLength 19; the route is a /32. Raise the maxLength, or add a ROA for 212.116.32.228/32.0 of 673
Route object: none212.116.32.228/32No route object for it. A route object for 212.116.32.0/19 with origin AS13170 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13170 in the RIR database for the space.0 of 673

Route objects not announced

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