bgpreport

Network · data from 2026-11-12

AS26934 UNIVERSITY-OF-MISSOURI---COLUMBIA - University of Missouri-Columbia

Registry name: UNIVERSITY-OF-MISSOURI---COLUMBIA - University of Missouri-Columbia, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26934, 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.
128.206.188.0/24 No ROA Nonecovered by 128.206.0.0/16 669 99% 68
128.206.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
161.130.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
198.209.48.0/20 Valid Other IRR onlyRADB 669 99% 68
207.160.151.0/24 Valid Other IRR onlyRADB 669 99% 68
207.160.152.0/21 Valid Other IRR onlyRADB 669 99% 68
209.106.228.0/22 Valid Other IRR onlyRADB 669 99% 68
2610:e0:a000::/48 Valid Other IRR onlyRADB 635 100% 70
2610:e0:a010::/44 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS26934 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 17 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none128.206.188.0/24No ROA covers it. Add a ROA for AS26934, maxLength 24.669 of 673
Route object: none128.206.188.0/24No route object for it. A route object for 128.206.0.0/16 with origin AS26934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26934 in the RIR database for the space.669 of 673
ROA: none128.206.0.0/16No ROA covers it. Add a ROA for AS26934, maxLength 16.669 of 673
Route object: RIR128.206.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none161.130.0.0/16No ROA covers it. Add a ROA for AS26934, maxLength 16.669 of 673
Route object: RIR161.130.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR198.209.48.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.160.151.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR207.160.152.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR209.106.228.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2610:e0:a000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2610:e0:a010::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

128.206.250.0/24RADBNo ROA
128.206.251.0/24RADBNo ROA
161.130.188.0/24RADBNo ROA
161.130.189.0/24RADBNo ROA
198.209.50.0/24RADBValid

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.