bgpreport

Network · data from 2026-11-12

AS33168 INLANDIMAGING - INLAND IMAGING L.L.C.

Registry name: INLANDIMAGING - INLAND IMAGING L.L.C., US · not in PeeringDB

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

Announced routes

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

192.69.104.0/24 No ROA Nonecovered by 192.69.104.0/21 673 100% 67
192.69.105.0/24 No ROA Nonecovered by 192.69.104.0/21 673 100% 67
192.69.110.0/24 No ROA Nonecovered by 192.69.104.0/21 673 100% 67
192.69.111.0/24 No ROA Nonecovered by 192.69.104.0/21 673 100% 67
192.69.106.0/24 No ROA Nonecovered by 192.69.104.0/21 672 100% 67
192.69.108.0/24 No ROA Nonecovered by 192.69.104.0/21 672 100% 67
192.69.109.0/24 No ROA Nonecovered by 192.69.104.0/21 672 100% 67
66.43.12.0/24 No ROA Nonecovered by 66.43.12.0/22 670 100% 67
208.66.96.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.97.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.98.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.99.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.100.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.101.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.102.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.66.103.0/24 No ROA Nonecovered by 208.66.96.0/21 669 99% 67
208.89.120.0/24 No ROA Nonecovered by 208.89.120.0/21 669 99% 67
208.89.121.0/24 No ROA Nonecovered by 208.89.120.0/21 669 99% 67
208.89.122.0/24 No ROA Nonecovered by 208.89.120.0/21 669 99% 67
208.89.123.0/24 No ROA Nonecovered by 208.89.120.0/21 669 99% 67
208.89.124.0/22 No ROA Nonecovered by 208.89.120.0/21 669 99% 67
192.69.107.0/24 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

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

  • ROA: none22
  • Route object: none21
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none192.69.104.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.673 of 673
Route object: none192.69.104.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.673 of 673
ROA: none192.69.105.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.673 of 673
Route object: none192.69.105.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.673 of 673
ROA: none192.69.110.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.673 of 673
Route object: none192.69.110.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.673 of 673
ROA: none192.69.111.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.673 of 673
Route object: none192.69.111.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.673 of 673
ROA: none192.69.106.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.672 of 673
Route object: none192.69.106.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.672 of 673
ROA: none192.69.108.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.672 of 673
Route object: none192.69.108.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.672 of 673
ROA: none192.69.109.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.672 of 673
Route object: none192.69.109.0/24No route object for it. A route object for 192.69.104.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.672 of 673
ROA: none66.43.12.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.670 of 673
Route object: none66.43.12.0/24No route object for it. A route object for 66.43.12.0/22 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.670 of 673
ROA: none208.66.96.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.96.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.97.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.97.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.98.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.98.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.99.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.99.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.100.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.100.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.101.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.101.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.102.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.102.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.66.103.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.66.103.0/24No route object for it. A route object for 208.66.96.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.89.120.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.89.120.0/24No route object for it. A route object for 208.89.120.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.89.121.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.89.121.0/24No route object for it. A route object for 208.89.120.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.89.122.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.89.122.0/24No route object for it. A route object for 208.89.120.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.89.123.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: none208.89.123.0/24No route object for it. A route object for 208.89.120.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none208.89.124.0/22No ROA covers it. Add a ROA for AS33168, maxLength 22.669 of 673
Route object: none208.89.124.0/22No route object for it. A route object for 208.89.120.0/21 with origin AS33168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33168 in the RIR database for the space.669 of 673
ROA: none192.69.107.0/24No ROA covers it. Add a ROA for AS33168, maxLength 24.669 of 673
Route object: RIR192.69.107.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

66.43.12.0/22RADBNo ROA
192.69.104.0/21RADBNo ROA
208.66.96.0/21RADBNo ROA
208.89.120.0/21RADBNo 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.