bgpreport

Network · data from 2026-11-12

AS5739 UCSC

Registry name: UCSC - University of California, Santa Cruz, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5739, 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.
137.164.3.48/31 No ROA None 1 0%low visibility 1
137.164.23.182/31 No ROA None 1 0%low visibility 1
2607:f380::118:9a40:3300/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:7b60/123 No ROA None 1 0%low visibility 1
169.233.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
128.114.0.0/16 No ROA Other IRR onlyRADB 667 99% 68
2607:f5f0::/32 Valid RIR databaseARIN, RADB 633 100% 69

AS-SET

AS5739's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none137.164.3.48/31No ROA covers it. Add a ROA for AS5739, maxLength 31.1 of 673
Route object: none137.164.3.48/31No route object for it. Add a route object with origin AS5739 in the RIR database for the space.1 of 673
ROA: none137.164.23.182/31No ROA covers it. Add a ROA for AS5739, maxLength 31.1 of 673
Route object: none137.164.23.182/31No route object for it. Add a route object with origin AS5739 in the RIR database for the space.1 of 673
ROA: none2607:f380::118:9a40:3300/123No ROA covers it. Add a ROA for AS5739, maxLength 123.1 of 636
Route object: none2607:f380::118:9a40:3300/123No route object for it. Add a route object with origin AS5739 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a41:7b60/123No ROA covers it. Add a ROA for AS5739, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:7b60/123No route object for it. Add a route object with origin AS5739 in the RIR database for the space.1 of 636
ROA: none169.233.0.0/16No ROA covers it. Add a ROA for AS5739, maxLength 16.669 of 673
Route object: RIR169.233.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none128.114.0.0/16No ROA covers it. Add a ROA for AS5739, maxLength 16.667 of 673
Route object: RIR128.114.0.0/16Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

192.35.220.0/24ARIN, RADBValid
192.35.223.0/24ARIN, RADBValid

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.