bgpreport

Network · data from 2026-11-12

AS11161 DIGITALVIRT

Registry name: DIGITALVIRT - DigitalVirt, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11161, 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.83.4.0/24 Invalid: origin None 1 0%low visibility 1
64.83.5.0/24 Invalid: origin None 1 0%low visibility 1
64.83.6.0/24 Invalid: origin Other origin only 1 0%low visibility 1
64.83.7.0/24 Invalid: origin None 1 0%low visibility 1
64.178.112.0/23 Invalid: origin Other origin only 1 0%low visibility 1
64.178.122.0/23 Invalid: origin Other origin only 1 0%low visibility 1
64.178.124.0/23 Invalid: origin Other origin only 1 0%low visibility 1
64.178.126.0/23 Invalid: origin Other origin only 1 0%low visibility 1
154.36.128.0/21 No ROA Other origin only 1 0%low visibility 1
151.241.128.0/24 Valid Nonecovered by 151.241.128.0/22 179 27% 55
2400:8a20:130::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS11161'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 24 are in fix.csv.

  • ROA: origin8
  • ROA: none1
  • Route object: none10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin64.83.4.0/24ROAs covering it name AS979, AS1014, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.83.4.0/24No route object for it. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.83.5.0/24ROAs covering it name AS979, AS1014, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.83.5.0/24No route object for it. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.83.6.0/24ROAs covering it name AS979, AS1014, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.83.6.0/24Route objects for it name AS1014. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.83.7.0/24ROAs covering it name AS979, AS1014, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.83.7.0/24No route object for it. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.178.112.0/23ROAs covering it name AS979, AS1014, AS400951, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.178.112.0/23Route objects for it name AS400951. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.178.122.0/23ROAs covering it name AS979, AS1014, AS400951, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.178.122.0/23Route objects for it name AS400951. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.178.124.0/23ROAs covering it name AS979, AS1014, AS400951, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.178.124.0/23Route objects for it name AS400951. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: origin64.178.126.0/23ROAs covering it name AS979, AS1014, AS400951, not AS11161. If AS11161 should announce it, add a ROA for AS11161.1 of 673
Route object: none64.178.126.0/23Route objects for it name AS400951. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
ROA: none154.36.128.0/21No ROA covers it. Add a ROA for AS11161, maxLength 21.1 of 673
Route object: none154.36.128.0/21Route objects for it name AS979. Add a route object with origin AS11161 in the RIR database for the space.1 of 673
Route object: none151.241.128.0/24No route object for it. A route object for 151.241.128.0/22 with origin AS11161 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11161 in the RIR database for the space.179 of 673

Route objects not announced

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

151.241.128.0/22RADB, RIPEValid
205.153.84.0/24RADBNo ROA
205.153.85.0/24RADBNo ROA
205.153.86.0/23RADBNo ROA
206.16.241.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.