bgpreport

Network · data from 2026-11-12

AS62618 Michigan Technological University

Registry name: MICHIGANTECH - Michigan Technological University, US · PeeringDB

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

Announced routes

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

44.103.48.0/23 No ROA Other IRR onlyRADB 671 100% 68
35.54.0.0/20 Valid Other IRR onlyRADB 673 100% 68
141.219.0.0/16 Valid Other IRR onlyRADB 670 100% 68

AS-SET

AS62618'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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none44.103.48.0/23No ROA covers it. Add a ROA for AS62618, maxLength 23.671 of 673
Route object: RIR44.103.48.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR35.54.0.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR141.219.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS62618 is announced.

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.