bgpreport

Network · data from 2026-11-12

AS25655 OSTK-COM - Overstock.com

Registry name: OSTK-COM - Overstock.com, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25655, 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.
65.116.112.0/21 No ROA Other IRR onlyRADB 672 100% 67
173.241.156.0/24 Valid RIR databaseARIN 673 100% 67
173.241.145.0/24 Valid RIR databaseARIN, RADB 672 100% 67
173.241.146.0/23 Valid RIR databaseARIN, RADB 672 100% 67
173.241.148.0/23 Valid RIR databaseARIN 672 100% 67
173.241.153.0/24 Valid RIR databaseARIN, RADB 672 100% 67
173.241.154.0/23 Valid RIR databaseARIN, RADB 672 100% 67
173.241.157.0/24 Valid RIR databaseARIN 672 100% 67
173.241.158.0/24 Valid RIR databaseARIN 672 100% 67
173.241.144.0/24 Valid RIR databaseARIN 671 100% 68
173.241.152.0/24 Valid RIR databaseARIN 671 100% 68
173.241.151.0/24 Valid RIR databaseARIN 2 0%low visibility 3

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none65.116.112.0/21No ROA covers it. Add a ROA for AS25655, maxLength 21.672 of 673
Route object: RIR65.116.112.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

67.110.104.0/21RADBNo ROA
173.241.144.0/20ARINValid

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.