bgpreport

Network · data from 2026-11-12

AS46853 SWTEXAS - Southwest Texas Communications

Registry name: SWTEXAS - Southwest Texas Communications, US · not in PeeringDB

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

Announced routes

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

63.174.144.0/22 No ROA None 671 100% 68
63.174.144.0/24 No ROA None 671 100% 68
63.174.145.0/24 No ROA None 671 100% 68
63.174.146.0/24 No ROA None 671 100% 68
208.23.136.0/24 No ROA None 671 100% 68
216.162.96.0/20 No ROA None 670 100% 69
63.174.134.0/24 No ROA None 669 99% 68
63.174.140.0/23 No ROA None 669 99% 68
63.174.140.0/24 No ROA None 669 99% 68
63.174.134.0/23 No ROA None 2 0%low visibility 2
63.174.142.0/24 No ROA None 2 0%low visibility 2
63.174.136.0/24 Valid Nonecovered by 63.174.136.0/22 671 100% 68
63.174.139.0/24 Valid Nonecovered by 63.174.136.0/22 671 100% 68
63.174.136.0/22 Valid RIR databaseARIN 671 100% 68
204.251.255.0/24 Valid RIR databaseARIN 671 100% 68

AS-SET

AS46853 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 24 are in fix.csv.

  • ROA: none11
  • Route object: none13
ChangePrefix or setDetailFull-table peers
ROA: none63.174.144.0/22No ROA covers it. Add a ROA for AS46853, maxLength 22.671 of 673
Route object: none63.174.144.0/22No route object for it. Add a route object with origin AS46853 in the RIR database for the space.671 of 673
ROA: none63.174.144.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.671 of 673
Route object: none63.174.144.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.671 of 673
ROA: none63.174.145.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.671 of 673
Route object: none63.174.145.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.671 of 673
ROA: none63.174.146.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.671 of 673
Route object: none63.174.146.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.671 of 673
ROA: none208.23.136.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.671 of 673
Route object: none208.23.136.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.671 of 673
ROA: none216.162.96.0/20No ROA covers it. Add a ROA for AS46853, maxLength 20.670 of 673
Route object: none216.162.96.0/20No route object for it. Add a route object with origin AS46853 in the RIR database for the space.670 of 673
ROA: none63.174.134.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.669 of 673
Route object: none63.174.134.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.669 of 673
ROA: none63.174.140.0/23No ROA covers it. Add a ROA for AS46853, maxLength 23.669 of 673
Route object: none63.174.140.0/23No route object for it. Add a route object with origin AS46853 in the RIR database for the space.669 of 673
ROA: none63.174.140.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.669 of 673
Route object: none63.174.140.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.669 of 673
ROA: none63.174.134.0/23No ROA covers it. Add a ROA for AS46853, maxLength 23.2 of 673
Route object: none63.174.134.0/23No route object for it. Add a route object with origin AS46853 in the RIR database for the space.2 of 673
ROA: none63.174.142.0/24No ROA covers it. Add a ROA for AS46853, maxLength 24.2 of 673
Route object: none63.174.142.0/24No route object for it. Add a route object with origin AS46853 in the RIR database for the space.2 of 673
Route object: none63.174.136.0/24No route object for it. A route object for 63.174.136.0/22 with origin AS46853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46853 in the RIR database for the space.671 of 673
Route object: none63.174.139.0/24No route object for it. A route object for 63.174.136.0/22 with origin AS46853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46853 in the RIR database for the space.671 of 673

Route objects not announced

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