bgpreport

Network · data from 2026-11-12

AS20126 UC-DOM - University of Cincinnati

Registry name: UC-DOM - University of Cincinnati, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20126, 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.137.28.0/24 No ROA Nonecovered by 129.137.0.0/16 20 3%low visibility 18
129.137.0.0/16 No ROA Other IRR onlyALTDB, RADB 671 100% 69

AS-SET

AS20126 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none129.137.28.0/24No ROA covers it. Add a ROA for AS20126, maxLength 24.20 of 673
Route object: none129.137.28.0/24No route object for it. A route object for 129.137.0.0/16 with origin AS20126 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20126 in the RIR database for the space.20 of 673
ROA: none129.137.0.0/16No ROA covers it. Add a ROA for AS20126, maxLength 16.671 of 673
Route object: RIR129.137.0.0/16Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2620:4:c000::/48RADBNo 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.