# Can't get Anchor MoneyMarket Contract configuration in Bombay-11

**URL:** <https://forum.anchorprotocol.com/t/cant-get-anchor-moneymarket-contract-configuration-in-bombay-11/1231>\
**Category:** General\
**Created:** [September 22, 2021, 8:42am UTC](https://forum.anchorprotocol.com/t/cant-get-anchor-moneymarket-contract-configuration-in-bombay-11/1231 "2021-09-22T08:42:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![riki](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.anchorprotocol.com/riki/32/250_2.png) [@riki](https://forum.anchorprotocol.com/u/riki)\
**Post date:** [September 22, 2021, 8:42am UTC](https://forum.anchorprotocol.com/t/cant-get-anchor-moneymarket-contract-configuration-in-bombay-11/1231/1 "2021-09-22T08:42:54Z")

</div>

`Bombay-11` was launched yesterday, and I found a problem with the `Bombay-11` TestNet.  
When I tried to query for getting Anchor MoneyMarket Contract config, it returns 500 error.

MoneyMarket Contract Address in `Bombay-11`:  
[https://finder.terra.money/bombay-11/address/terra15dwd5mj8v59wpj0wvt233mf5efdff808c5tkal](https://finder.terra.money/bombay-11/address/terra15dwd5mj8v59wpj0wvt233mf5efdff808c5tkal)  
query: `{"config": {}} `

Expected result: Returns the Anchor MoneyMarket Contract configuration

Current status: It returns status code 500

I tried to query on `Tequila-004` TestNet and `Columbus-4` MainNet, and it worked well.  
Also, this query was working well on the `Bombay-10` TestNet, but doesn’t work after launched `Bombay-11`.  
How can I solve this problem? Let me know your suggestion.

---

<div class="post-metadata">

**Author:** ![riki](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.anchorprotocol.com/riki/32/250_2.png) [@riki](https://forum.anchorprotocol.com/u/riki)\
**Post date:** [September 23, 2021, 8:29am UTC](https://forum.anchorprotocol.com/t/cant-get-anchor-moneymarket-contract-configuration-in-bombay-11/1231/2 "2021-09-23T08:29:36Z")

</div>

It was resolved on Sep 23th.  
Anchor Protocol dev team launched anchor on `bombay-11` today and this issue was resolved.  
Thank you Anchor Protocol Team for a quick fix.
