bgpreport

Network · data from 2026-11-12

AS398940 USA-NETWORKING - University of South Alabama

Registry name: USA-NETWORKING - University of South Alabama, US · not in PeeringDB

12IPv4 routes 91.7% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS398940, seen from no peer

Announced routes

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

142.249.156.0/23 No ROA RIR databaseARIN, RADB 664 99% 68
192.245.222.0/24 Valid Other IRR onlyRADB 664 99% 68
192.245.223.0/24 Valid Other IRR onlyRADB 664 99% 68
199.33.130.0/24 Valid Other IRR onlyRADB 664 99% 68
199.33.131.0/24 Valid Other IRR onlyRADB 664 99% 68
199.33.132.0/24 Valid Other IRR onlyRADB 664 99% 68
199.33.133.0/24 Valid Other IRR onlyRADB 664 99% 68
69.85.215.0/24 Valid Other IRR onlyRADB 663 99% 68
69.85.217.0/24 Valid Other IRR onlyRADB 663 99% 68
192.245.221.0/24 Valid RIR databaseARIN, RADB 664 99% 68
192.245.224.0/24 Valid RIR databaseARIN, RADB 664 99% 68
199.33.134.0/24 Valid RIR databaseARIN, RADB 664 99% 68
2607:db40::/32 Valid RIR databaseARIN 631 99% 68

AS-SET

AS398940 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none142.249.156.0/23No ROA covers it. Add a ROA for AS398940, maxLength 23.664 of 673
Route object: RIR192.245.222.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR192.245.223.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR199.33.130.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR199.33.131.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR199.33.132.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR199.33.133.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR69.85.215.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR69.85.217.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673

Route objects not announced

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

69.85.216.0/24RADBValid
192.245.222.0/23ARIN, RADBValid
199.33.130.0/23ARIN, RADBValid
199.33.132.0/23ARIN, RADBValid
2604:27a0::/32ARINNo 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.