Network · data from 2026-11-12

AS152479 DELTA SOFTWARE AND COMMUNICATION

Registry name: DSACL-AS-AP - DELTA SOFTWARE AND COMMUNICATION LIMITED, BD · PeeringDB

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

31IPv6 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 AS152479, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS152479, 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.66.168.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.124.110.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.126.148.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.126.151.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.150.19.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.158.119.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.224.55.0/24	Valid	RIR databaseAPNIC	673 100%	69
165.101.12.0/24	Valid	RIR databaseAPNIC	673 100%	69
103.133.207.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.158.118.0/24	Valid	RIR databaseAPNIC	672 100%	69
2403:8840::/33	Valid	RIR databaseAPNIC	635 100%	69
2403:8840::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:1::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:2::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:3::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:4::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:5::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:6::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:7::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:8::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:9::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:a::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:b::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:c::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:d::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:e::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:f::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:10::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:11::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:12::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:13::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:14::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:15::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:16::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:17::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:18::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:19::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:1a::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:1b::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:1c::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:8840:1d::/48	Valid	RIR databaseAPNIC	635 100%	69
103.158.118.0/23	Valid	RIR databaseAPNIC	403 60%	65

AS-SET

PeeringDB's irr_as_set for AS152479: AS152479:AS-DSCL. 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 (AS152479 isn't in the set, or no route object for AS152479 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	AS152479 in it	Not covered
AS152479:AS-DSCL	APNIC	2	1	44	Yes	0

Name

Database

ASNs

Sets

Route objects

AS152479 in it

Not covered

AS152479:AS-DSCL

APNIC

Yes

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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