bgpreport

Network · data from 2026-11-12

AS25612 DSL-EXPRESS

Registry name: DSL-EXPRESS - DSL EXPRESS, US · PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
40Route objects not announced registered with origin AS25612, seen from no peer

Announced routes

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

64.238.16.0/20 No ROA Other IRR onlyRADB 671 100% 68
66.251.197.0/24 No ROA Other IRR onlyRADB 671 100% 68
72.0.107.0/24 No ROA Other IRR onlyRADB 671 100% 68
209.150.0.0/19 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS25612's PeeringDB record names no 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 47 are in fix.csv.

  • ROA: none4
  • Route object: RIR3
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
ROA: none64.238.16.0/20No ROA covers it. Add a ROA for AS25612, maxLength 20.671 of 673
Route object: RIR64.238.16.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.251.197.0/24No ROA covers it. Add a ROA for AS25612, maxLength 24.671 of 673
Route object: RIR66.251.197.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none72.0.107.0/24No ROA covers it. Add a ROA for AS25612, maxLength 24.671 of 673
Route object: RIR72.0.107.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none209.150.0.0/19No ROA covers it. Add a ROA for AS25612, maxLength 19.671 of 673

Route objects not announced

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

63.161.157.0/24RADBNo ROA
63.163.60.0/24RADBNo ROA
63.167.202.0/24RADBNo ROA
63.168.114.0/24RADBNo ROA
63.172.66.0/24RADBNo ROA
64.238.16.0/21RADBNo ROA
64.238.16.0/22RADBNo ROA
64.238.16.0/23RADBNo ROA
64.238.16.0/24RADBNo ROA
64.238.17.0/24RADBNo ROA
64.238.18.0/23RADBNo ROA
64.238.18.0/24RADBNo ROA
64.238.19.0/24RADBNo ROA
64.238.20.0/22RADBNo ROA
64.238.20.0/23RADBNo ROA
64.238.20.0/24RADBNo ROA
64.238.21.0/24RADBNo ROA
64.238.22.0/23RADBNo ROA
64.238.22.0/24RADBNo ROA
64.238.23.0/24RADBNo ROA
64.238.24.0/21RADBNo ROA
64.238.24.0/22RADBNo ROA
64.238.24.0/23RADBNo ROA
64.238.24.0/24RADBNo ROA
64.238.25.0/24RADBNo ROA
64.238.26.0/23RADBNo ROA
64.238.26.0/24RADBNo ROA
64.238.27.0/24RADBNo ROA
64.238.28.0/22RADBNo ROA
64.238.28.0/23RADBNo ROA
64.238.28.0/24RADBNo ROA
64.238.29.0/24RADBNo ROA
64.238.30.0/23RADBNo ROA
64.238.30.0/24RADBNo ROA
64.238.31.0/24RADBNo ROA
65.169.169.0/24RADBNo ROA
65.174.220.0/24RADBNo ROA
205.160.205.0/24RADBNo ROA
208.21.11.0/24RADBNo ROA
208.35.16.0/24RADBNo ROA

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.