bgpreport

Network · data from 2026-11-12

AS10381 Southwest Cyberport

Registry name: SWCP-AS - Southwest Cyberport, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10381, 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.
192.160.121.0/24 No ROA None 672 100% 67
198.49.44.0/24 No ROA None 672 100% 67
198.51.249.0/24 No ROA Other origin only 2 0%low visibility 2
198.49.217.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.59.115.0/24 No ROA Other IRR onlyRADB 669 99% 68
204.29.236.0/24 No ROA Other IRR onlyRADB 669 99% 68
64.42.128.0/20 No ROA RIR databaseARIN 669 99% 68
64.42.160.0/20 No ROA RIR databaseARIN 669 99% 68
69.49.160.0/20 No ROA RIR databaseARIN, RADB 669 99% 68
216.184.0.0/19 No ROA RIR databaseARIN 669 99% 68
2001:1800::/32 No ROA RIR databaseARIN 636 100% 67

AS-SET

AS10381's PeeringDB record names no 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: none11
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none192.160.121.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.672 of 673
Route object: none192.160.121.0/24No route object for it. Add a route object with origin AS10381 in the RIR database for the space.672 of 673
ROA: none198.49.44.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.672 of 673
Route object: none198.49.44.0/24No route object for it. Add a route object with origin AS10381 in the RIR database for the space.672 of 673
ROA: none198.51.249.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.2 of 673
Route object: none198.51.249.0/24Route objects for it name AS6993, AS40498. Add a route object with origin AS10381 in the RIR database for the space.2 of 673
ROA: none198.49.217.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.669 of 673
Route object: RIR198.49.217.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.59.115.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.669 of 673
Route object: RIR198.59.115.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none204.29.236.0/24No ROA covers it. Add a ROA for AS10381, maxLength 24.669 of 673
Route object: RIR204.29.236.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none64.42.128.0/20No ROA covers it. Add a ROA for AS10381, maxLength 20.669 of 673
ROA: none64.42.160.0/20No ROA covers it. Add a ROA for AS10381, maxLength 20.669 of 673
ROA: none69.49.160.0/20No ROA covers it. Add a ROA for AS10381, maxLength 20.669 of 673
ROA: none216.184.0.0/19No ROA covers it. Add a ROA for AS10381, maxLength 19.669 of 673
ROA: none2001:1800::/32No ROA covers it. Add a ROA for AS10381, maxLength 32.636 of 636

Route objects not announced

Every route object with origin AS10381 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.