bgpreport

Network · data from 2026-11-12

AS131464 Digi Jadoo Broadband

Registry name: DJBL-AS-AP - Digi Jadoo Broadband Ltd, BD · PeeringDB

35IPv4 routes 94.3% RPKI valid · 94.3% with a route object
49IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 2 with no route object for this origin
46Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS131464, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131464, 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.156.176.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.167.17.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.69.149.0/24 Valid RIR databaseAPNIC 673 100% 67
103.69.150.0/24 Valid RIR databaseAPNIC 673 100% 69
103.154.159.0/24 Valid RIR databaseAPNIC 673 100% 69
103.198.133.0/24 Valid RIR databaseAPNIC 673 100% 70
103.115.242.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.233.0/24 Valid RIR databaseAPNIC 672 100% 67
180.149.235.0/24 Valid RIR databaseAPNIC 672 100% 67
103.69.148.0/22 Valid RIR databaseAPNIC 671 100% 66
103.69.148.0/23 Valid RIR databaseAPNIC 671 100% 67
103.69.148.0/24 Valid RIR databaseAPNIC 671 100% 67
103.69.150.0/23 Valid RIR databaseAPNIC 671 100% 66
103.109.96.0/22 Valid RIR databaseAPNIC 671 100% 66
103.109.96.0/24 Valid RIR databaseAPNIC 671 100% 67
103.109.98.0/23 Valid RIR databaseAPNIC 671 100% 66
103.115.242.0/23 Valid RIR databaseAPNIC 671 100% 67
103.115.243.0/24 Valid RIR databaseAPNIC 671 100% 67
103.198.134.0/23 Valid RIR databaseAPNIC 671 100% 66
114.129.13.0/24 Valid RIR databaseAPNIC 671 100% 67
161.248.205.0/24 Valid RIR databaseAPNIC 671 100% 67
163.52.23.0/24 Valid RIR databaseAPNIC 671 100% 68
180.149.232.0/22 Valid RIR databaseAPNIC 671 100% 66
180.149.232.0/23 Valid RIR databaseAPNIC 671 100% 66
180.149.232.0/24 Valid RIR databaseAPNIC 671 100% 67
180.149.234.0/23 Valid RIR databaseAPNIC 671 100% 66
180.149.234.0/24 Valid RIR databaseAPNIC 671 100% 67
202.12.123.0/24 Valid RIR databaseAPNIC 671 100% 68
103.147.191.0/24 Valid RIR databaseAPNIC 670 100% 68
103.109.98.0/24 Valid RIR databaseAPNIC 669 99% 67
103.109.99.0/24 Valid RIR databaseAPNIC 669 99% 67
103.198.134.0/24 Valid RIR databaseAPNIC 669 99% 67
2405:f280:1::/48 Valid RIR databaseAPNIC 636 100% 67
2405:f280:14::/48 Valid RIR databaseAPNIC 636 100% 67
2405:f280:34::/48 Valid RIR databaseAPNIC 636 100% 70
2405:f280:192::/48 Valid RIR databaseAPNIC 636 100% 70
2405:f280:e034::/48 Valid RIR databaseAPNIC 636 100% 67
2405:f280:ef00::/48 Valid RIR databaseAPNIC 636 100% 67
2405:f280::/32 Valid RIR databaseAPNIC 635 100% 71
103.198.135.0/24 Valid RIR databaseAPNIC 107 16% 39
103.69.151.0/24 Valid RIR databaseAPNIC 14 2%low visibility 9
2405:f280::/33 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280::/34 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:11::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:1000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:2000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:2000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:3000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:4000::/34 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:4000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:4000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:5000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:6000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:6000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:7000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:8000::/33 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:8000::/34 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:8000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:8000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:9000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:9000::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:a000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:a000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:b000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:c000::/34 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:c000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:c000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:c002::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:d000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:e000::/35 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:e000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:f000::/36 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff00::/40 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff00::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff01::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff02::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff03::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff04::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff05::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff06::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
2405:f280:ff07::/48 Valid RIR databaseAPNIC 1 0%low visibility 1
103.198.132.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS131464: AS-131464. 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 (AS131464 isn't in the set, or no route object for AS131464 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.

NameDatabaseASNsSets Route objectsAS131464 in itNot covered
AS-131464 APNIC 94114,609 Yes 2

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

  • ROA: origin2
  • Route object: none2
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: origin103.156.176.0/24ROAs covering it name AS134734, not AS131464. If AS131464 should announce it, add a ROA for AS131464.0 of 673
Route object: none103.156.176.0/24Route objects for it name AS134734. Add a route object with origin AS131464 in the RIR database for the space.0 of 673
ROA: origin103.167.17.0/24ROAs covering it name AS134734, not AS131464. If AS131464 should announce it, add a ROA for AS131464.0 of 673
Route object: none103.167.17.0/24Route objects for it name AS134734. Add a route object with origin AS131464 in the RIR database for the space.0 of 673

Route objects not announced

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

103.109.96.0/23APNICValid
103.109.97.0/24APNICValid
2405:f280:3::/48APNICValid
2405:f280:5c::/48APNICValid
2405:f280:1000::/48APNICValid
2405:f280:1001::/48APNICValid
2405:f280:1038::/48APNICValid
2405:f280:1039::/48APNICValid
2405:f280:9001::/48APNICValid
2405:f280:c000::/48APNICValid
2405:f280:c001::/48APNICValid
2405:f280:c100::/48APNICValid
2405:f280:c102::/48APNICValid
2405:f280:e000::/48APNICValid
2405:f280:e004::/48APNICValid
2405:f280:e005::/48APNICValid
2405:f280:e006::/48APNICValid
2405:f280:e007::/48APNICValid
2405:f280:e008::/48APNICValid
2405:f280:e009::/48APNICValid
2405:f280:e00a::/48APNICValid
2405:f280:e00b::/48APNICValid
2405:f280:e00c::/48APNICValid
2405:f280:e00d::/48APNICValid

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.