bgpreport

Network · data from 2026-11-12

AS18454 AUGSBURG - Augsburg University

Registry name: AUGSBURG - Augsburg University, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18454, 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.
141.224.0.0/18 No ROA RIR databaseARIN 670 100% 69
141.224.64.0/19 No ROA RIR databaseARIN 670 100% 69
141.224.96.0/20 No ROA RIR databaseARIN 670 100% 69

AS-SET

AS18454 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 4 are in fix.csv.

  • ROA: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none141.224.0.0/18No ROA covers it. Add a ROA for AS18454, maxLength 18.670 of 673
ROA: none141.224.64.0/19No ROA covers it. Add a ROA for AS18454, maxLength 19.670 of 673
ROA: none141.224.96.0/20No ROA covers it. Add a ROA for AS18454, maxLength 20.670 of 673

Route objects not announced

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

2001:470:48e::/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.