bgpreport

Network · data from 2026-11-12

AS25706 INTERLINKCI-AS1 - Interlink Connectivity Inc

Registry name: INTERLINKCI-AS1 - Interlink Connectivity Inc, CA · not in PeeringDB

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

Announced routes

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

206.108.4.0/24 No ROA Other origin onlycovered by 206.108.4.0/22 672 100% 67
206.108.6.0/24 No ROA Nonecovered by 206.108.4.0/22 672 100% 67
192.139.81.0/24 No ROA Other IRR onlyBELL, RADB 672 100% 67
206.108.7.0/24 No ROA Other IRR onlyRADB 672 100% 67
208.67.144.0/21 No ROA Other IRR onlyBELL, RADB 672 100% 67

AS-SET

AS25706 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 17 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none206.108.4.0/24No ROA covers it. Add a ROA for AS25706, maxLength 24.672 of 673
Route object: none206.108.4.0/24Route objects for it name AS395322. A route object for 206.108.4.0/22 with origin AS25706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25706 in the RIR database for the space.672 of 673
ROA: none206.108.6.0/24No ROA covers it. Add a ROA for AS25706, maxLength 24.672 of 673
Route object: none206.108.6.0/24No route object for it. A route object for 206.108.4.0/22 with origin AS25706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25706 in the RIR database for the space.672 of 673
ROA: none192.139.81.0/24No ROA covers it. Add a ROA for AS25706, maxLength 24.672 of 673
Route object: RIR192.139.81.0/24Route object only in BELL, RADB. Add it in the RIR database for the space.672 of 673
ROA: none206.108.7.0/24No ROA covers it. Add a ROA for AS25706, maxLength 24.672 of 673
Route object: RIR206.108.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.67.144.0/21No ROA covers it. Add a ROA for AS25706, maxLength 21.672 of 673
Route object: RIR208.67.144.0/21Route object only in BELL, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

192.139.80.0/24BELLNo ROA
192.234.254.0/24BELL, RADBNo ROA
199.202.202.0/23BELLNo ROA
204.225.106.0/24BELLNo ROA
204.225.177.0/24BELLNo ROA
205.189.41.0/24BELLNo ROA
206.108.4.0/22BELL, RADBNo 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.