Network · data from 2026-11-12

AS60557 Alpine North Networks

Registry name: ALPINE-NORTH-AS Krik van der Vinne trading as Alpine North, NL · PeeringDB

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

6IPv6 routes 66.7% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

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

2Route objects not announced registered with origin AS60557, seen from no peer

Announced routes

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


2a0d:8d06::/32	No ROA	RIR databaseRIPE	636 100%	69
2a0e:fd45:da0::/48	No ROA	RIR databaseRIPE	636 100%	69
176.119.215.0/24	Valid	RIR databaseRIPE	673 100%	67
2001:678:ce4::/48	Valid	RIR databaseRIPE	636 100%	69
2001:678:ce8::/48	Valid	RIR databaseRIPE	636 100%	69
2001:678:cec::/48	Valid	RIR databaseRIPE	636 100%	69
2001:678:cf0::/48	Valid	RIR databaseRIPE	636 100%	69

AS-SET

PeeringDB's irr_as_set for AS60557: RIPE::AS-ALPINE-NORTH. 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 (AS60557 isn't in the set, or no route object for AS60557 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	AS60557 in it	Not covered
RIPE::AS-ALPINE-NORTH	RIPElists itself further down1 member set in no database: AS197814:AS-BITTNER	95	18	1,440	Yes	0

Name

Database

ASNs

Sets

Route objects

AS60557 in it

Not covered

RIPE::AS-ALPINE-NORTH

RIPElists itself further down1 member set in no database: AS197814:AS-BITTNER

1,440

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.

ROA: none2
AS-SET: missing member1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a0d:8d06::/32	No ROA covers it. Add a ROA for AS60557, maxLength 32.	636 of 636
ROA: none	2a0e:fd45:da0::/48	No ROA covers it. Add a ROA for AS60557, maxLength 48.	636 of 636
AS-SET: missing member	RIPE::AS-ALPINE-NORTH	AS-ALPINE-NORTH (RIPE) lists AS197814:AS-BITTNER; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a0d:8d06::/32

No ROA covers it. Add a ROA for AS60557, maxLength 32.

636 of 636

ROA: none

2a0e:fd45:da0::/48

No ROA covers it. Add a ROA for AS60557, maxLength 48.

636 of 636

AS-SET: missing member

RIPE::AS-ALPINE-NORTH

AS-ALPINE-NORTH (RIPE) lists AS197814:AS-BITTNER; no IRR database read has it.

Route objects not announced

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


2a0e:fd40:200::/48	RIPE	No ROA
2a0e:fd45:da0::/43	RIPE	No ROA

2a0e:fd40:200::/48

RIPE

No ROA

2a0e:fd45:da0::/43

RIPE

No ROA

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.