Network · data from 2026-11-12

AS17212 TRI-COUNTY-FIBER-COMMUNICATIONS - Tri-County Fiber Communications, LLC

Registry name: TRI-COUNTY-FIBER-COMMUNICATIONS - Tri-County Fiber Communications, LLC, US · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 50.0% with a route object

1IPv6 routes 0.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

5No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS17212, seen from no peer

Announced routes

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


103.209.56.0/22	No ROA	Other origin only	671 100%	69
170.4.200.0/21	No ROA	Other origin only	671 100%	69
2606:76c0::/32	No ROA	Other origin only	636 100%	67
152.86.240.0/21	No ROA	Other IRR onlyRADB	671 100%	68
152.86.248.0/21	No ROA	Other IRR onlyRADB	671 100%	68

AS-SET

AS17212 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 10 are in fix.csv.

ROA: none5
Route object: none3
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.209.56.0/22	No ROA covers it. Add a ROA for AS17212, maxLength 22.	671 of 673
Route object: none	103.209.56.0/22	Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.	671 of 673
ROA: none	170.4.200.0/21	No ROA covers it. Add a ROA for AS17212, maxLength 21.	671 of 673
Route object: none	170.4.200.0/21	Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.	671 of 673
ROA: none	2606:76c0::/32	No ROA covers it. Add a ROA for AS17212, maxLength 32.	636 of 636
Route object: none	2606:76c0::/32	Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.	636 of 636
ROA: none	152.86.240.0/21	No ROA covers it. Add a ROA for AS17212, maxLength 21.	671 of 673
Route object: RIR	152.86.240.0/21	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	152.86.248.0/21	No ROA covers it. Add a ROA for AS17212, maxLength 21.	671 of 673
Route object: RIR	152.86.248.0/21	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.209.56.0/22

No ROA covers it. Add a ROA for AS17212, maxLength 22.

671 of 673

Route object: none

103.209.56.0/22

Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.

671 of 673

ROA: none

170.4.200.0/21

No ROA covers it. Add a ROA for AS17212, maxLength 21.

671 of 673

Route object: none

170.4.200.0/21

Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.

671 of 673

ROA: none

2606:76c0::/32

No ROA covers it. Add a ROA for AS17212, maxLength 32.

636 of 636

Route object: none

2606:76c0::/32

Route objects for it name AS11758. Add a route object with origin AS17212 in the RIR database for the space.

636 of 636

ROA: none

152.86.240.0/21

No ROA covers it. Add a ROA for AS17212, maxLength 21.

671 of 673

Route object: RIR

152.86.240.0/21

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

ROA: none

152.86.248.0/21

No ROA covers it. Add a ROA for AS17212, maxLength 21.

671 of 673

Route object: RIR

152.86.248.0/21

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

Every route object with origin AS17212 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.