bgpreport

Network · data from 2026-11-12

AS8036 University of Tulsa

Registry name: UTULSA-AS - University of Tulsa, US · PeeringDB

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

Announced routes

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

129.244.210.0/24 No ROA Nonecovered by 129.244.128.0/17 668 99% 69
129.244.0.0/17 No ROA Other IRR onlyRADB 670 100% 70
129.244.128.0/17 No ROA Other IRR onlyRADB 670 100% 70
2605:e340::/40 No ROA Other IRR onlyRADB 634 100% 70

AS-SET

AS8036'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 10 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none129.244.210.0/24No ROA covers it. Add a ROA for AS8036, maxLength 24.668 of 673
Route object: none129.244.210.0/24No route object for it. A route object for 129.244.128.0/17 with origin AS8036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8036 in the RIR database for the space.668 of 673
ROA: none129.244.0.0/17No ROA covers it. Add a ROA for AS8036, maxLength 17.670 of 673
Route object: RIR129.244.0.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none129.244.128.0/17No ROA covers it. Add a ROA for AS8036, maxLength 17.670 of 673
Route object: RIR129.244.128.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2605:e340::/40No ROA covers it. Add a ROA for AS8036, maxLength 40.634 of 636
Route object: RIR2605:e340::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

129.244.0.0/16RADBNo ROA
2605:e340::/32RADBNo 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.