bgpreport

Network · data from 2026-11-12

AS154107 DGNL-AS-AP - DigitalLink Global Network Limited

Registry name: DGNL-AS-AP - DigitalLink Global Network Limited, HK · not in PeeringDB

18IPv4 routes 77.8% RPKI valid · 72.2% with a route object
0IPv6 routes
4RPKI invalid 2 origin · 2 maxLength
0No ROA 5 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS154107, seen from no peer

Announced routes

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

157.254.191.0/24 Invalid: origin Other origin only 4 1%low visibility 3
69.33.210.0/23 Invalid: origin RIR databaseARIN, RADB 2 0%low visibility 1
69.33.212.0/24 Invalid: maxLength Nonecovered by 69.33.212.0/23 25 4%low visibility 15
69.33.213.0/24 Invalid: maxLength Nonecovered by 69.33.212.0/23 25 4%low visibility 15
203.12.254.0/24 Valid Nonecovered by 203.12.254.0/23 672 100% 67
203.12.255.0/24 Valid Nonecovered by 203.12.254.0/23 672 100% 67
203.12.254.0/23 Valid Other IRR onlyRADB 672 100% 67
45.202.199.0/24 Valid Other IRR onlyRADB 4 1%low visibility 3
61.18.136.0/21 Valid RIR databaseAPNIC, RADB 672 100% 67
61.18.136.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.137.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.138.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.139.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.140.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.141.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.142.0/24 Valid RIR databaseAPNIC 672 100% 67
61.18.143.0/24 Valid RIR databaseAPNIC 672 100% 67
69.33.212.0/23 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS154107 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • ROA: origin2
  • ROA: maxLength2
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin157.254.191.0/24ROAs covering it name AS834, not AS154107. If AS154107 should announce it, add a ROA for AS154107.4 of 673
Route object: none157.254.191.0/24Route objects for it name AS834. Add a route object with origin AS154107 in the RIR database for the space.4 of 673
ROA: origin69.33.210.0/23ROAs covering it name AS834, not AS154107. If AS154107 should announce it, add a ROA for AS154107.2 of 673
ROA: maxLength69.33.212.0/24ROA 69.33.212.0/23 AS154107 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 69.33.212.0/24.25 of 673
Route object: none69.33.212.0/24No route object for it. A route object for 69.33.212.0/23 with origin AS154107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154107 in the RIR database for the space.25 of 673
ROA: maxLength69.33.213.0/24ROA 69.33.212.0/23 AS154107 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 69.33.213.0/24.25 of 673
Route object: none69.33.213.0/24No route object for it. A route object for 69.33.212.0/23 with origin AS154107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154107 in the RIR database for the space.25 of 673
Route object: none203.12.254.0/24No route object for it. A route object for 203.12.254.0/23 with origin AS154107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154107 in the RIR database for the space.672 of 673
Route object: none203.12.255.0/24No route object for it. A route object for 203.12.254.0/23 with origin AS154107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154107 in the RIR database for the space.672 of 673
Route object: RIR203.12.254.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.202.199.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673

Route objects not announced

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

61.18.136.0/22APNICValid
61.18.136.0/23APNICValid
61.18.138.0/23APNICValid
61.18.140.0/22APNICValid
61.18.140.0/23APNICValid
61.18.142.0/23APNICValid

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.