bgpreport

Network · data from 2026-11-12

AS32312 TELECOMSYS-PUBLIC - Telecommunication Systems, Inc.

Registry name: TELECOMSYS-PUBLIC - Telecommunication Systems, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32312, 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.
216.221.128.0/21 No ROA Other origin only 672 100% 67
216.221.136.0/21 No ROA Other origin only 672 100% 67
66.159.105.0/24 No ROA Other IRR onlyRADB 672 100% 67
66.159.104.0/24 No ROA Other IRR onlyRADB 671 100% 66
205.159.29.0/24 No ROA RIR databaseARIN, RADB 673 100% 66
204.87.180.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
64.58.176.0/24 Valid None 671 100% 67
64.58.182.0/24 Valid None 671 100% 67
64.146.185.0/24 Valid RIR databaseARIN 672 100% 67
209.210.15.0/24 Valid RIR databaseARIN, RADB 672 100% 67
209.210.26.0/24 Valid RIR databaseARIN 672 100% 67
64.146.184.0/24 Valid RIR databaseARIN, RADB 671 100% 66

AS-SET

AS32312 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none216.221.128.0/21No ROA covers it. Add a ROA for AS32312, maxLength 21.672 of 673
Route object: none216.221.128.0/21Route objects for it name AS19905. Add a route object with origin AS32312 in the RIR database for the space.672 of 673
ROA: none216.221.136.0/21No ROA covers it. Add a ROA for AS32312, maxLength 21.672 of 673
Route object: none216.221.136.0/21Route objects for it name AS19905. Add a route object with origin AS32312 in the RIR database for the space.672 of 673
ROA: none66.159.105.0/24No ROA covers it. Add a ROA for AS32312, maxLength 24.672 of 673
Route object: RIR66.159.105.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none66.159.104.0/24No ROA covers it. Add a ROA for AS32312, maxLength 24.671 of 673
Route object: RIR66.159.104.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.159.29.0/24No ROA covers it. Add a ROA for AS32312, maxLength 24.673 of 673
ROA: none204.87.180.0/24No ROA covers it. Add a ROA for AS32312, maxLength 24.672 of 673
Route object: none64.58.176.0/24No route object for it. Add a route object with origin AS32312 in the RIR database for the space.671 of 673
Route object: none64.58.182.0/24No route object for it. Add a route object with origin AS32312 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS32312 is announced.

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.