bgpreport

Network · data from 2026-11-12

AS402215 DEVOLOGY - Devology Tech LLC

Registry name: DEVOLOGY - Devology Tech LLC, US · not in PeeringDB

42IPv4 routes 7.1% RPKI valid · 7.1% with a route object
0IPv6 routes
37RPKI invalid 37 origin · 0 maxLength
2No ROA 39 with no route object for this origin
39Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS402215, seen from no peer

Announced routes

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

5.182.112.0/24 Invalid: origin None 2 0%low visibility 2
31.58.33.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.25.47.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.27.95.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.108.208.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.109.152.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.110.51.0/24 Invalid: origin None 2 0%low visibility 2
82.153.101.0/24 Invalid: origin Other origin only 2 0%low visibility 2
83.98.194.0/24 Invalid: origin Other origin only 2 0%low visibility 2
85.92.140.0/24 Invalid: origin Other origin only 2 0%low visibility 2
85.222.198.0/24 Invalid: origin Other origin only 2 0%low visibility 2
87.84.211.0/24 Invalid: origin None 2 0%low visibility 2
87.86.208.0/24 Invalid: origin None 2 0%low visibility 2
88.209.227.0/24 Invalid: origin Other origin only 2 0%low visibility 2
89.30.159.0/24 Invalid: origin Other origin only 2 0%low visibility 2
89.207.178.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.205.87.0/24 Invalid: origin Other origin only 2 0%low visibility 2
109.66.19.0/24 Invalid: origin Other origin only 2 0%low visibility 2
141.11.79.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.242.174.0/24 Invalid: origin Other origin only 2 0%low visibility 2
164.37.194.0/24 Invalid: origin Other origin only 2 0%low visibility 2
194.77.78.0/24 Invalid: origin Other origin only 2 0%low visibility 2
194.77.91.0/24 Invalid: origin Other origin only 2 0%low visibility 2
213.189.22.0/24 Invalid: origin Other origin only 2 0%low visibility 2
213.247.45.0/24 Invalid: origin Other origin only 2 0%low visibility 2
16.216.19.0/24 Invalid: origin Other origin only 1 0%low visibility 1
45.87.175.0/24 Invalid: origin Other origin only 1 0%low visibility 1
79.172.250.0/24 Invalid: origin Other origin only 1 0%low visibility 1
79.183.2.0/24 Invalid: origin None 1 0%low visibility 1
81.168.64.0/24 Invalid: origin Other origin only 1 0%low visibility 1
157.254.154.0/24 Invalid: origin Other origin only 1 0%low visibility 1
191.101.9.0/24 Invalid: origin Other origin only 1 0%low visibility 1
192.6.55.0/24 Invalid: origin Other origin only 1 0%low visibility 1
192.120.199.0/24 Invalid: origin Other origin only 1 0%low visibility 1
194.77.26.0/24 Invalid: origin Other origin only 1 0%low visibility 1
195.72.169.0/24 Invalid: origin Other origin only 1 0%low visibility 1
212.180.108.0/24 Invalid: origin Other origin only 1 0%low visibility 1
95.214.39.0/24 No ROA Other origin only 2 0%low visibility 2
185.212.113.0/24 No ROA Other origin only 2 0%low visibility 2
109.64.0.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
178.92.117.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
186.241.178.0/24 Valid RIR databaseRADB, RIPE 671 100% 66

AS-SET

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

  • ROA: origin37
  • ROA: none2
  • Route object: none39
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin5.182.112.0/24ROAs covering it name AS25198, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none5.182.112.0/24No route object for it. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin31.58.33.0/24ROAs covering it name AS138077, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none31.58.33.0/24Route objects for it name AS138077. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.25.47.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.25.47.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.27.95.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.27.95.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.108.208.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.108.208.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.109.152.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.109.152.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.110.51.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.110.51.0/24No route object for it. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin82.153.101.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none82.153.101.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin83.98.194.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none83.98.194.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin85.92.140.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none85.92.140.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin85.222.198.0/24ROAs covering it name AS8315, AS214036, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none85.222.198.0/24Route objects for it name AS214036. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin87.84.211.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none87.84.211.0/24No route object for it. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin87.86.208.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none87.86.208.0/24No route object for it. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin88.209.227.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none88.209.227.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin89.30.159.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none89.30.159.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin89.207.178.0/24ROAs covering it name AS834, AS61317, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none89.207.178.0/24Route objects for it name AS834, AS61317. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin103.205.87.0/24ROAs covering it name AS63902, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none103.205.87.0/24Route objects for it name AS63902. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin109.66.19.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none109.66.19.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin141.11.79.0/24ROAs covering it name AS138995, AS199779, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none141.11.79.0/24Route objects for it name AS138995, AS199779. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin151.242.174.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none151.242.174.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin164.37.194.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none164.37.194.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin194.77.78.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none194.77.78.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin194.77.91.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none194.77.91.0/24Route objects for it name AS834, AS3257. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin213.189.22.0/24ROAs covering it name AS834, AS8315, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none213.189.22.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin213.247.45.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.2 of 673
Route object: none213.247.45.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: origin16.216.19.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none16.216.19.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin45.87.175.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none45.87.175.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin79.172.250.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none79.172.250.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin79.183.2.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none79.183.2.0/24No route object for it. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin81.168.64.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none81.168.64.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin157.254.154.0/24ROAs covering it name AS401142, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none157.254.154.0/24Route objects for it name AS401142. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin191.101.9.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none191.101.9.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin192.6.55.0/24ROAs covering it name AS2856, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none192.6.55.0/24Route objects for it name AS2856. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin192.120.199.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none192.120.199.0/24Route objects for it name AS834, AS16276. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin194.77.26.0/24ROAs covering it name AS198566, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none194.77.26.0/24Route objects for it name AS3257, AS198566. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin195.72.169.0/24ROAs covering it name AS13537, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none195.72.169.0/24Route objects for it name AS13537. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: origin212.180.108.0/24ROAs covering it name AS834, not AS402215. If AS402215 should announce it, add a ROA for AS402215.1 of 673
Route object: none212.180.108.0/24Route objects for it name AS834, AS3257. Add a route object with origin AS402215 in the RIR database for the space.1 of 673
ROA: none95.214.39.0/24No ROA covers it. Add a ROA for AS402215, maxLength 24.2 of 673
Route object: none95.214.39.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673
ROA: none185.212.113.0/24No ROA covers it. Add a ROA for AS402215, maxLength 24.2 of 673
Route object: none185.212.113.0/24Route objects for it name AS834. Add a route object with origin AS402215 in the RIR database for the space.2 of 673

Route objects not announced

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

154.94.50.0/24AFRINICInvalid: origin
154.202.101.0/24AFRINICInvalid: origin
156.225.72.0/24AFRINICInvalid: origin
192.82.174.0/24ARIN, RADBValid
192.120.43.0/24ARIN, RADBValid
192.132.201.0/24ARIN, RADBValid

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.