bgpreport

Network · data from 2026-11-12

AS209274 Kraken Network ISP

Registry name: Kraken-Network-ISP Kraken Network ISP LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209274, 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.

31.59.151.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.243.109.0/24 Invalid: origin Other origin only 2 0%low visibility 2
163.5.102.0/24 Invalid: origin Other origin only 2 0%low visibility 2
169.40.135.0/24 Invalid: origin Other origin only 2 0%low visibility 2

AS-SET

AS209274's PeeringDB record names no AS-SET.

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: origin4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin31.59.151.0/24ROAs covering it name AS219509, not AS209274. If AS209274 should announce it, add a ROA for AS209274.2 of 673
Route object: none31.59.151.0/24Route objects for it name AS219509. Add a route object with origin AS209274 in the RIR database for the space.2 of 673
ROA: origin151.243.109.0/24ROAs covering it name AS834, not AS209274. If AS209274 should announce it, add a ROA for AS209274.2 of 673
Route object: none151.243.109.0/24Route objects for it name AS834. Add a route object with origin AS209274 in the RIR database for the space.2 of 673
ROA: origin163.5.102.0/24ROAs covering it name AS834, not AS209274. If AS209274 should announce it, add a ROA for AS209274.2 of 673
Route object: none163.5.102.0/24Route objects for it name AS834. Add a route object with origin AS209274 in the RIR database for the space.2 of 673
ROA: origin169.40.135.0/24ROAs covering it name AS834, not AS209274. If AS209274 should announce it, add a ROA for AS209274.2 of 673
Route object: none169.40.135.0/24Route objects for it name AS834. Add a route object with origin AS209274 in the RIR database for the space.2 of 673

Route objects not announced

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