Network · data from 2026-11-12

AS62417 DIGITALK

Registry name: DIGITALK_CLOUD_THW DIGITALK Limited, GB · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object

0IPv6 routes

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


185.231.78.47/32	Invalid: maxLength	Nonecovered by 185.231.78.0/24	2 0%low visibility	5
103.180.243.0/24	Valid	RIR databaseAPNIC	673 100%	67
185.32.78.0/24	Valid	RIR databaseRIPE	673 100%	67
185.32.79.0/24	Valid	RIR databaseRIPE	673 100%	67
185.231.78.0/24	Valid	RIR databaseRIPE	673 100%	67
185.231.79.0/24	Valid	RIR databaseRIPE	673 100%	67

185.231.78.47/32

Invalid: maxLength

Nonecovered by 185.231.78.0/24

2 0%low visibility

103.180.243.0/24

Valid

RIR databaseAPNIC

673 100%

185.32.78.0/24

Valid

RIR databaseRIPE

673 100%

185.32.79.0/24

Valid

RIR databaseRIPE

673 100%

185.231.78.0/24

Valid

RIR databaseRIPE

673 100%

185.231.79.0/24

Valid

RIR databaseRIPE

673 100%

AS-SET

PeeringDB's irr_as_set for AS62417: AS62417:AS-DIGITALK-CLOUD-THW. 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 (AS62417 isn't in the set, or no route object for AS62417 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	AS62417 in it	Not covered
AS62417:AS-DIGITALK-CLOUD-THW	RIPE	1	1	5	Yes	1

Name

Database

ASNs

Sets

Route objects

AS62417 in it

Not covered

AS62417:AS-DIGITALK-CLOUD-THW

RIPE

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

ROA: maxLength1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	185.231.78.47/32	ROA 185.231.78.0/24 AS62417 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.231.78.47/32.	2 of 673
Route object: none	185.231.78.47/32	No route object for it. A route object for 185.231.78.0/24 with origin AS62417 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62417 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

185.231.78.47/32

ROA 185.231.78.0/24 AS62417 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.231.78.47/32.

2 of 673

Route object: none

185.231.78.47/32

No route object for it. A route object for 185.231.78.0/24 with origin AS62417 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62417 in the RIR database for the space.

2 of 673

Route objects not announced

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