Network · data from 2026-11-12
AS32274 LENAWEE-MONROE-TECHNOLOGY-CONSORTIUM - Lenawee-Monroe Technology Consortium
Registry name: LENAWEE-MONROE-TECHNOLOGY-CONSORTIUM - Lenawee-Monroe Technology Consortium, US · not in PeeringDB
27IPv4 routes
96.3% RPKI valid · 11.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
1No ROA
24 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS32274, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS32274, 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.
| 207.190.160.0/19 | No ROA | RIR databaseARIN | 670 100% |
| 207.190.160.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.161.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.162.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.163.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.164.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.166.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.167.0/24 | Valid | Nonecovered by 207.190.160.0/21 | 670 100% |
| 207.190.168.0/24 | Valid | Nonecovered by 207.190.168.0/22 | 670 100% |
| 207.190.169.0/24 | Valid | Nonecovered by 207.190.168.0/22 | 670 100% |
| 207.190.170.0/24 | Valid | Nonecovered by 207.190.168.0/22 | 670 100% |
| 207.190.171.0/24 | Valid | Nonecovered by 207.190.168.0/22 | 670 100% |
| 207.190.176.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.177.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.178.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.179.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.180.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.181.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.182.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.183.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.184.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.185.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.187.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.191.0/24 | Valid | Nonecovered by 207.190.176.0/20 | 670 100% |
| 207.190.175.0/24 | Valid | Nonecovered by 207.190.174.0/23 | 669 99% |
| 207.190.173.0/24 | Valid | RIR databaseARIN | 670 100% |
| 207.190.188.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS32274 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 30 are in fix.csv.
- ROA: none1
- Route object: none24
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.190.160.0/19 | No ROA covers it. Add a ROA for AS32274, maxLength 19. |
| Route object: none | 207.190.160.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.161.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.162.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.163.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.164.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.166.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.167.0/24 | No route object for it. A route object for 207.190.160.0/21 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.168.0/24 | No route object for it. A route object for 207.190.168.0/22 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.169.0/24 | No route object for it. A route object for 207.190.168.0/22 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.170.0/24 | No route object for it. A route object for 207.190.168.0/22 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.171.0/24 | No route object for it. A route object for 207.190.168.0/22 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.176.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.177.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.178.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.179.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.180.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.181.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.182.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.183.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.184.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.185.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.187.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.191.0/24 | No route object for it. A route object for 207.190.176.0/20 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
| Route object: none | 207.190.175.0/24 | No route object for it. A route object for 207.190.174.0/23 with origin AS32274 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32274 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32274 whose prefix no peer sees AS32274 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 207.190.160.0/21 | ARIN | Valid |
| 207.190.168.0/22 | ARIN | Valid |
| 207.190.174.0/23 | ARIN | No ROA |
| 207.190.176.0/20 | ARIN | Valid |
| 2620:11b:1000::/40 | ARIN, RADB | Valid |
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.