bgpreport

Network · data from 2026-11-12

AS393698 SW-USA-LLC - SW USA LLC

Registry name: SW-USA-LLC - SW USA LLC, US · not in PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS393698, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS393698, 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.
66.46.176.0/21 Valid Other IRR onlyALTDB, RADB 672 100% 67
207.126.101.0/24 Valid Other IRR onlyALTDB 672 100% 67
206.72.120.0/23 Valid RIR databaseALTDB, ARIN 673 100% 67
206.72.122.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
173.46.144.0/24 Valid RIR databaseALTDB, ARIN 672 100% 67
173.46.145.0/24 Valid RIR databaseALTDB, ARIN 672 100% 67
173.46.146.0/24 Valid RIR databaseALTDB, ARIN 672 100% 67
173.46.147.0/24 Valid RIR databaseALTDB, ARIN 672 100% 67
206.72.116.0/22 Valid RIR databaseARIN 672 100% 67
206.72.123.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67

AS-SET

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

  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR66.46.176.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR207.126.101.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

64.55.172.0/24ALTDBNo ROA
74.115.204.0/22RADBNo ROA
173.46.144.0/20RADBNo ROA
199.244.76.0/22RADBNo ROA
206.72.112.0/20RADBNo 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.