Polygon/MATIC Status Update

Update 7/12/2021 – The issue is resolved!
To see the current network status, please visit our new System Status page.


  • We are experiencing a delay in reading your liquidity pools entries and exits on the Polygon blockchain due to the increased blocks and growing data and also the slow indexing from The Graph. 
  • We are working on an optimized version of our subgraph and also allowing you to manually add transactions in the meantime.
  • If you recently provided liquidity or removed liquidity, you might not see those transactions but we are working to resolve this ASAP. If you haven’t added or removed liquidity recently, then this won’t affect you (we are showing you the current prices).

MATIC Status Update

When working on the cutting edge of technology, sometimes things do not go as planned. At APY.Vision we try to be innovative and push the envelope of what we can do. We are not just a team of developers, we are also eager users of crypto projects of all shapes and sizes. We say that because it also affects us when something goes wrong on the APY.Vision website. 

We acknowledge that we have had some serious problems getting reliable data on the MATIC chain lately. This is not the standard which we consider acceptable and are working diligently behind the scenes to try to come up with a solution for the issue of MATIC data being unavailable, so we can get the most up to date data from the MATIC chain.

To be fair, this issue is not limited to APY.Vision, there have been interruptions and incomplete data for almost all of the websites attempting to track in-depth Polygon data. The Polygon/MATIC version of SushiSwap recently put up this warning pictured below to address the same issue.

Warning on the Polygon version of SushiSwap
Warning on the Polygon version of SushiSwap

What the issue is

The Polygon/MATIC network has been experiencing some growing pains lately. The high profile rise and fall of the Iron Finance project and the TITAN token even ensnared billionaire Mark Cuban. There was a mad rush to exit the protocol which caused a lot of extra activity on the network as some nefarious actors were spamming the network with empty transactions as liquidity providers were trying to exit their positions. The MATIC network is already resource intensive due to the fast two second block times, but during this period 40GB of transaction data was being added to the chain each day, making it extremely difficult to sync with. Pictured below is an example of the spam transactions that were clogging the network.

We, along with many other projects, rely on The Graph to index the MATIC blockchain. The Graph is struggling to keep up with the MATIC chain which causes our data feed to experience delays. This only applies to the MATIC data, the Ethereum portion of the site is still working as intended. We understand this causes a degraded user experience and we are working hard to come up with a solution for this issue.

How we’re addressing it

We are tackling this problem from a number of angles to improve the end user experience. We wrote a new optimized version of our subgraph to improve efficiency. This subgraph has almost completed indexing and we expect it to be ready any day now.  

In addition to the subgraph improvements, we will be adding a new “Status Page” to APY.Vision so there is a place to check the indexing status for each network we support and the current price data status. This will allow end users to verify if price data is up to date or not.

UPDATE: Status Page is now active!

We also are planning to make optimizations to our backend to reduce the possibility of events like this disrupting service. We can do that by limiting the amount of data we need to call from the blockchain and other such optimizations that will improve data availability and reliability. 

Finally, we will be allowing users to add in transactions manually, for when the data is still being indexed and we can’t see the liquidity pool entries/exits yet.

We thank all of our users for their patience as we try to work out this problem. We understand the frustrations it is causing and are working hard to remedy the issue.

The APY.Vision team