# Price feed issues \[resolved\]

**URL:** <https://bisq.community/t/price-feed-issues-resolved/3683>\
**Category:** Support\
**Created:** [December 8, 2017, 5:55am UTC](https://bisq.community/t/price-feed-issues-resolved/3683 "2017-12-08T05:55:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 8, 2017, 5:55am UTC](https://bisq.community/t/price-feed-issues-resolved/3683/1 "2017-12-08T05:55:14Z")

</div>

We have currently problems to get the Fiat prices from BitcoinAverage on 2 of 3 price relay nodes. I banned the 2 nodes which don’t deliver Fiat prices and we are in contact with BitcoinAverage to resolve the issue. As soon that works again the ban will be lifted. That is just to avoid that users connect to those nodes which dont have Fiat prices atm.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 8, 2017, 6:13am UTC](https://bisq.community/t/price-feed-issues-resolved/3683/2 "2017-12-08T06:13:52Z")

</div>

Damn, seems that the only remaining working node also dont get data anymore.  
So fiat trades with % based price are atm not possible. Sorry for the inconvenience and I hope we can that soon resolved.

Show another single point of failure we need to fix:

> <https://github.com/bisq-network/bisq/issues/1074>
>
> We are very dependent on BitcoinAverage as the only Fiat price provider. If ther…e are issues (as we just faced) all percentage based prices cannot be taken.
> We need secondary price sources and either fall back to that in case we have issues with BitcoinAverage or mix it. Thought there is some complexity as all price relays need to have the same source as otherwise take offer attempts can fail if the price what the maker and the taker sees is above a small tolerance window. E.g. If one peer gets the price from a relay which gets it from BitcoinAverage and the other peer is connected to a relay which is connected to coinmarketcap the price will be likely different and exceeds the tolerance window.
> So it need some creative solution how to deal with those issues.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [December 8, 2017, 1:21pm UTC](https://bisq.community/t/price-feed-issues-resolved/3683/3 "2017-12-08T13:21:31Z")

</div>

Issues is resolved. BitcoinAverage had an issues with it’s loadbalancer.