bgpreport

Network · data from 2026-11-12

AS33091 U Calgary

Registry name: U-CALGARY - University of Calgary, CA · 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
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS33091, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33091, 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.
198.161.243.0/24 No ROA Other IRR onlyCANARIE 669 99% 68
136.159.0.0/16 Valid RIR databaseARIN, CANARIE 671 100% 68
198.161.127.0/24 Valid RIR databaseARIN, CANARIE 21 3%low visibility 18

AS-SET

AS33091'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 3 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none198.161.243.0/24No ROA covers it. Add a ROA for AS33091, maxLength 24.669 of 673
Route object: RIR198.161.243.0/24Route object only in CANARIE. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

2620:42:e000::/48ARINValid

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.