bgpreport

Network · data from 2026-11-12

AS30059 ZIMCOM

Registry name: ZIMCOM - Zimcom Network Solutions Inc., US · PeeringDB

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

Announced routes

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

70.36.35.0/24 No ROA Nonecovered by 70.36.32.0/20 671 100% 68
70.36.36.0/24 No ROA Nonecovered by 70.36.32.0/20 671 100% 68
70.36.37.0/24 No ROA Nonecovered by 70.36.32.0/20 671 100% 68
70.36.38.0/24 No ROA Nonecovered by 70.36.32.0/20 671 100% 68
209.212.252.0/24 No ROA Nonecovered by 209.212.240.0/20 671 100% 68
209.212.255.0/24 No ROA Other origin onlycovered by 209.212.240.0/20 671 100% 68
209.212.250.0/23 No ROA Nonecovered by 209.212.240.0/20 2 0%low visibility 2
70.36.32.0/20 No ROA Other IRR onlyALTDB, RADB 671 100% 68
207.250.172.0/23 No ROA Other IRR onlyALTDB, RADB 671 100% 68
209.212.240.0/20 No ROA Other IRR onlyALTDB, RADB 671 100% 68
66.42.206.0/24 Valid RIR databaseALTDB, ARIN 671 100% 68
66.161.141.0/24 Valid RIR databaseARIN, RADB 671 100% 68
69.61.246.0/23 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68
69.61.248.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68
216.68.76.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68
216.68.232.0/23 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68

AS-SET

AS30059'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: none10
  • Route object: none7
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none70.36.35.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none70.36.35.0/24No route object for it. A route object for 70.36.32.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none70.36.36.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none70.36.36.0/24No route object for it. A route object for 70.36.32.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none70.36.37.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none70.36.37.0/24No route object for it. A route object for 70.36.32.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none70.36.38.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none70.36.38.0/24No route object for it. A route object for 70.36.32.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none209.212.252.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none209.212.252.0/24No route object for it. A route object for 209.212.240.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none209.212.255.0/24No ROA covers it. Add a ROA for AS30059, maxLength 24.671 of 673
Route object: none209.212.255.0/24Route objects for it name AS40832. A route object for 209.212.240.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.671 of 673
ROA: none209.212.250.0/23No ROA covers it. Add a ROA for AS30059, maxLength 23.2 of 673
Route object: none209.212.250.0/23No route object for it. A route object for 209.212.240.0/20 with origin AS30059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30059 in the RIR database for the space.2 of 673
ROA: none70.36.32.0/20No ROA covers it. Add a ROA for AS30059, maxLength 20.671 of 673
Route object: RIR70.36.32.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none207.250.172.0/23No ROA covers it. Add a ROA for AS30059, maxLength 23.671 of 673
Route object: RIR207.250.172.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none209.212.240.0/20No ROA covers it. Add a ROA for AS30059, maxLength 20.671 of 673
Route object: RIR209.212.240.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

38.119.219.0/24ALTDB, RADBNo ROA
70.36.32.0/24RADBNo ROA
70.36.34.0/24RADBNo ROA
2607:f550::/32ALTDBNo 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.