bgpreport

Network · data from 2026-11-12

AS62775 INTERNET2-ISS - Internet2

Registry name: INTERNET2-ISS - Internet2, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62775, 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.
2001:468:1f22::/48 No ROA None 2 0%low visibility 2
163.253.26.0/23 Valid Other IRR onlyRADB 672 100% 68
163.253.60.0/23 Valid Other IRR onlyRADB 672 100% 68
2001:468:1f20::/48 Valid Other IRR onlyRADB 636 100% 68
2001:468:1f21::/48 Valid Other IRR onlyRADB 636 100% 68
163.253.68.0/23 Valid Other IRR onlyRADB 11 2%low visibility 11

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2001:468:1f22::/48No ROA covers it. Add a ROA for AS62775, maxLength 48.2 of 636
Route object: none2001:468:1f22::/48No route object for it. Add a route object with origin AS62775 in the RIR database for the space.2 of 636
Route object: RIR163.253.26.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR163.253.60.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:468:1f20::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:468:1f21::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR163.253.68.0/23Route object only in RADB. Add it in the RIR database for the space.11 of 673

Route objects not announced

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

163.253.26.0/24RADBValid
163.253.27.0/24RADBValid
163.253.60.0/24RADBValid
163.253.61.0/24RADBValid

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.