bgpreport

Network · data from 2026-11-12

AS13326 TUFTS-UNIVERSITY - Tufts University

Registry name: TUFTS-UNIVERSITY - Tufts University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13326, 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.
130.64.0.0/16 No ROA Other IRR onlyRADB 671 100% 68
2607:f570::/32 No ROA Other IRR onlyRADB 418 66% 66

AS-SET

AS13326 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: none2
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none130.64.0.0/16No ROA covers it. Add a ROA for AS13326, maxLength 16.671 of 673
Route object: RIR130.64.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f570::/32No ROA covers it. Add a ROA for AS13326, maxLength 32.418 of 636
Route object: RIR2607:f570::/32Route object only in RADB. Add it in the RIR database for the space.418 of 636

Route objects not announced

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

38.97.110.208/29RADBNo ROA
130.64.19.0/24RADBNo ROA
130.64.25.0/24RADBNo ROA
130.64.111.0/24RADBNo ROA
130.64.112.0/24RADBNo ROA
130.64.156.0/24RADBNo ROA
130.64.212.0/24RADBNo ROA
130.64.213.0/24RADBNo 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.