bgpreport

Network · data from 2026-11-12

AS13998 SWMED - University of Texas Southwestern Medical Center

Registry name: SWMED - University of Texas Southwestern Medical Center, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13998, 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.112.109.0/24 No ROA Nonecovered by 129.112.0.0/16 668 99% 68
129.112.115.0/24 No ROA Nonecovered by 129.112.0.0/16 668 99% 68
198.241.16.0/20 No ROA Other IRR onlyRADB 670 100% 68
129.112.0.0/16 No ROA Other IRR onlyRADB 668 99% 68
199.165.152.0/23 No ROA Other IRR onlyRADB 668 99% 68
199.165.154.0/24 No ROA Other IRR onlyRADB 668 99% 68
199.242.234.0/23 No ROA Other IRR onlyRADB 668 99% 68
199.242.236.0/22 No ROA Other IRR onlyRADB 668 99% 68
199.249.214.0/24 No ROA Other IRR onlyRADB 668 99% 68
2620:0:840::/48 No ROA Other IRR onlyRADB 634 100% 70
198.215.48.0/20 Valid RIR databaseARIN, RADB 670 100% 68
198.215.96.0/20 Valid RIR databaseARIN, RADB 670 100% 68
198.215.176.0/20 Valid RIR databaseARIN, RADB 670 100% 68
198.215.36.0/22 Valid RIR databaseARIN, RADB 668 99% 68

AS-SET

AS13998 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none129.112.109.0/24No ROA covers it. Add a ROA for AS13998, maxLength 24.668 of 673
Route object: none129.112.109.0/24No route object for it. A route object for 129.112.0.0/16 with origin AS13998 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13998 in the RIR database for the space.668 of 673
ROA: none129.112.115.0/24No ROA covers it. Add a ROA for AS13998, maxLength 24.668 of 673
Route object: none129.112.115.0/24No route object for it. A route object for 129.112.0.0/16 with origin AS13998 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13998 in the RIR database for the space.668 of 673
ROA: none198.241.16.0/20No ROA covers it. Add a ROA for AS13998, maxLength 20.670 of 673
Route object: RIR198.241.16.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none129.112.0.0/16No ROA covers it. Add a ROA for AS13998, maxLength 16.668 of 673
Route object: RIR129.112.0.0/16Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none199.165.152.0/23No ROA covers it. Add a ROA for AS13998, maxLength 23.668 of 673
Route object: RIR199.165.152.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none199.165.154.0/24No ROA covers it. Add a ROA for AS13998, maxLength 24.668 of 673
Route object: RIR199.165.154.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none199.242.234.0/23No ROA covers it. Add a ROA for AS13998, maxLength 23.668 of 673
Route object: RIR199.242.234.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none199.242.236.0/22No ROA covers it. Add a ROA for AS13998, maxLength 22.668 of 673
Route object: RIR199.242.236.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none199.249.214.0/24No ROA covers it. Add a ROA for AS13998, maxLength 24.668 of 673
Route object: RIR199.249.214.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2620:0:840::/48No ROA covers it. Add a ROA for AS13998, maxLength 48.634 of 636
Route object: RIR2620:0:840::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS13998 is announced.

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.