# Inaccurate prices

**URL:** <https://forum.alpaca.markets/t/inaccurate-prices/14687>\
**Category:** Alpaca Trading\
**Created:** [July 22, 2024, 9:08am UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687 "2024-07-22T09:08:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petr\_Zajic](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/petr_zajic/32/5834_2.png) [@Petr\_Zajic](https://forum.alpaca.markets/u/Petr_Zajic)\
**Post date:** [July 22, 2024, 9:08am UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/1 "2024-07-22T09:08:53Z")

</div>

![Snímek obrazovky 2024-07-22 110819](https://us1.discourse-cdn.com/flex020/uploads/alp/original/2X/4/4c7dd47c2fdb881c7fb7d6988c4fdfd2f19421d0.jpeg)

---

<div class="post-metadata">

**Author:** ![rel91](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@rel91](https://forum.alpaca.markets/u/rel91)\
**Post date:** [July 22, 2024, 9:12am UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/2 "2024-07-22T09:12:06Z")

</div>

Similar issue I see is with JPM right now, this broke all my automations. What is the reason for this?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/alp/original/2X/6/60dd86be01772558a2bdc396e385c7c687f56e29.png)

---

<div class="post-metadata">

**Author:** ![Petr\_Zajic](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/petr_zajic/32/5834_2.png) [@Petr\_Zajic](https://forum.alpaca.markets/u/Petr_Zajic)\
**Post date:** [July 22, 2024, 10:20am UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/3 "2024-07-22T10:20:29Z")

</div>

and with several other tickers, alpaca, why ???  
 ![Snímek obrazovky 2024-07-22 121926](https://us1.discourse-cdn.com/flex020/uploads/alp/original/2X/5/5f6c911a5ff8870603f937ee80baa36cfca55d2e.jpeg)

---

<div class="post-metadata">

**Author:** ![rel91](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@rel91](https://forum.alpaca.markets/u/rel91)\
**Post date:** [July 22, 2024, 11:49am UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/4 "2024-07-22T11:49:52Z")

</div>

Looks like this was already noticed: [https://status.alpaca.markets/](https://status.alpaca.markets/)

---

<div class="post-metadata">

**Author:** ![Dan\_Whitnable\_Alpaca](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/dan_whitnable_alpaca/32/1658_2.png) [@Dan\_Whitnable\_Alpaca](https://forum.alpaca.markets/u/Dan_Whitnable_Alpaca)\
**Post date:** [July 22, 2024, 1:53pm UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/5 "2024-07-22T13:53:09Z")

</div>

@Petr_Zajic Apologies. The incorrect market data should be fixed soon (if not already). The issue stemmed from test data sent over the weekend by Alpaca’s data provider. Typically these test trades and quotes are filtered out and don’t get into the live data. The root cause has been identified and resolved and the Data Team is now simply working to patch the data with the correct trades and bars.

---

<div class="post-metadata">

**Author:** ![rel91](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@rel91](https://forum.alpaca.markets/u/rel91)\
**Post date:** [July 22, 2024, 4:00pm UTC](https://forum.alpaca.markets/t/inaccurate-prices/14687/6 "2024-07-22T16:00:41Z")

</div>

@Dan_Whitnable_Alpaca thanks for the reply. In my case, this looked like a huge loss on my active position and my automation tried to close all positions. (just a safety feature I have in my script). In case of loss or profit due to API faults does Alpaca take any responsibility?
