bgpreport

Network · data from 2026-11-12

AS194 UCAR-AS - University Corporation for Atmospheric Research

Registry name: UCAR-AS - University Corporation for Atmospheric Research, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS194, 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.117.0.0/16 Valid RIR databaseARIN, RADB 670 100% 68
128.117.208.0/22 Valid RIR databaseARIN 668 99% 68
192.43.244.0/24 Valid RIR databaseARIN, RADB 668 99% 68
192.52.106.0/24 Valid RIR databaseARIN, RADB 668 99% 68
2620:117:2000::/40 Valid RIR databaseARIN, RADB 635 100% 68
129.19.156.0/24 Valid RIR databaseARIN 20 3%low visibility 18

AS-SET

AS194 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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

192.188.155.0/24RADBNo ROA
2620:117:20f1::/48ARINInvalid: maxLength

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.