Network · data from 2026-11-12

AS134599 Digital Dot Net (DDN)

Registry name: DIGITALDOTNET-AS-AP - Digital Dot Net (DDN), BD · PeeringDB

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

16IPv6 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 AS134599, seen from no peer

Announced routes

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


103.70.170.0/24	Valid	RIR databaseAPNIC	673 100%	70
103.121.36.0/24	Valid	RIR databaseAPNIC	673 100%	70
103.121.37.0/24	Valid	RIR databaseAPNIC	673 100%	70
103.121.39.0/24	Valid	RIR databaseAPNIC	673 100%	70
103.135.91.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.136.107.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.140.204.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.177.139.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.179.58.0/24	Valid	RIR databaseAPNIC	673 100%	70
103.121.38.0/24	Valid	RIR databaseAPNIC	670 100%	67
2404:5fc0::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:1000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:2000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:3000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:4000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:5000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:6000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:7000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:8000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:9000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:a000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:b000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:c000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:d000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:e000::/36	Valid	RIR databaseAPNIC	636 100%	69
2404:5fc0:f000::/36	Valid	RIR databaseAPNIC	636 100%	69

AS-SET

PeeringDB's irr_as_set for AS134599: AS134599:AS-DDN. 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 (AS134599 isn't in the set, or no route object for AS134599 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	AS134599 in it	Not covered
AS134599:AS-DDN	APNIC	153	1	3,797	No	26

Name

Database

ASNs

Sets

Route objects

AS134599 in it

Not covered

AS134599:AS-DDN

APNIC

153

3,797

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.

AS-SET: own ASN1

Change	Prefix or set	Detail	Full-table peers
AS-SET: own ASN	AS134599:AS-DDN	AS134599 isn't in AS134599:AS-DDN (APNIC) once expanded. Add AS134599 to it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: own ASN

AS134599:AS-DDN

AS134599 isn't in AS134599:AS-DDN (APNIC) once expanded. Add AS134599 to it.

Route objects not announced

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