Network · data from 2026-11-12

AS219185 NARWHAL-NETTECH

Registry name: NARWHAL-NETTECH NARWHAL NETTECH LIMITED, GB · PeeringDB

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

3IPv6 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

0Route objects not announced registered with origin AS219185, seen from no peer

Announced routes

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


82.110.112.0/24	Valid	Other IRR onlyRADB	671 100%	68
164.37.208.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
2a06:9801:f1c::/48	Valid	RIR databaseRIPE	636 100%	69
2a0f:6280:1001::/48	Valid	RIR databaseRIPE	634 100%	68
2a13:9500:1ab::/48	Valid	RIR databaseRIPE	634 100%	69

AS-SET

AS219185'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 1 are in fix.csv.

Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	82.110.112.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

82.110.112.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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