bgpreport

Network · data from 2026-11-12

AS25970 IAC - IAC Services LLC

Registry name: IAC - IAC Services LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25970, 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.
65.255.0.0/20 No ROA Other origin onlycovered by 65.255.0.0/19 672 100% 67
65.255.16.0/20 No ROA Other origin onlycovered by 65.255.0.0/19 672 100% 67
65.255.0.0/19 No ROA Other IRR onlyNTTCOM 672 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none65.255.0.0/20No ROA covers it. Add a ROA for AS25970, maxLength 20.672 of 673
Route object: none65.255.0.0/20Route objects for it name AS7819. A route object for 65.255.0.0/19 with origin AS25970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25970 in the RIR database for the space.672 of 673
ROA: none65.255.16.0/20No ROA covers it. Add a ROA for AS25970, maxLength 20.672 of 673
Route object: none65.255.16.0/20Route objects for it name AS7819. A route object for 65.255.0.0/19 with origin AS25970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25970 in the RIR database for the space.672 of 673
ROA: none65.255.0.0/19No ROA covers it. Add a ROA for AS25970, maxLength 19.672 of 673
Route object: RIR65.255.0.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

66.180.32.0/19NTTCOMNo 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.