All Systems Operational
NFTX App ? Operational
90 days ago
95.75 % uptime
Today
API NFTX Token List Operational
90 days ago
100.0 % uptime
Today
NFTX Blog Operational
90 days ago
100.0 % uptime
Today
NFTX Docs Operational
90 days ago
100.0 % uptime
Today
NFTX Vault Contracts Operational
90 days ago
100.0 % uptime
Today
GitHub GitHub Pages Operational
GitHub Webhooks Operational
GitHub API Requests Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
API Token Lists
Fetching
Metadata API (via OpenSea)
Fetching
Past Incidents
Sep 27, 2022

No incidents reported today.

Sep 26, 2022

No incidents reported.

Sep 25, 2022

No incidents reported.

Sep 24, 2022

No incidents reported.

Sep 23, 2022

No incidents reported.

Sep 22, 2022

No incidents reported.

Sep 21, 2022

No incidents reported.

Sep 20, 2022

No incidents reported.

Sep 19, 2022

No incidents reported.

Sep 18, 2022

No incidents reported.

Sep 17, 2022

No incidents reported.

Sep 16, 2022
Resolved - With a bleeding-edge patch applied to one of our Erigon nodes the NFTX Graph Indexer was able to resync the NFTX subgraph.

The site is now running as expected, and we will continue to closely monitor the service over the weekend.

Sep 16, 21:31 UTC
Identified - There is an issue with the way in which Erigon is dealing with `trace_block` since the merge. This is resulting in a number of subgraphs that use trace to fail at the same block.

We have tried to switch our indexer from Erigon to GETH to fix the issue, however GETH does not support trace so the subgraph still fails.

Some updates have been made to the subgraph to remove the reliance on trace and a new subgraph has been deployed to test if this can fix the issue, the sync for this is looking to be 8-12 hours.

It is now a race between Erigon pushing a fix for this we can patch our nodes and resume indexing, or once the new subgraph deployment is fully indexed and tested then we can update the endpoints.

In the meantime we have reverted requests for the holdings to fallback to Web3 calls. This means that the vaults will load initially with the subgraph data before updating to show only items that are currenlty held in the vaults.

NFTX will still not be able to show any recent activity or newly created vaults on the UI.

Sep 16, 11:21 UTC
Update - This appears to be an issue relating to both The Graph and Erigon.

We applied https://github.com/ledgerwatch/erigon/commit/15ad43e1000e29e48f11de26aa42ebde72050772 patch however there were not improvements.

There are some indexers which are able to index to the current block now so we are looking at whether those will begin to return the up-to-date data for the apps.

Sep 16, 09:32 UTC
Investigating - The NFTX subgraph (along with a number of other subgraphs) is failingin on block `15539509`.

This is unrelated to the protocol being paused and likely linked to the recent merge.

The Graph team is looking into the issue and we're awaiting further updates from them.

You will still be able to interact with the app however data related to the holdings, recent transactions, activity etc may be incorrect (i.e. it will be showing the state of the platform as of block `15539509`).

Sep 15, 21:20 UTC
Sep 15, 2022
Resolved - This incident has been resolved.

You can read more on https://blog.nftx.io/postmortem-nftxmarketplace0xzap-vulnerability/

Sep 15, 21:15 UTC
Monitoring - The fix has been pushed and we're unpausing the contracts now.
Sep 15, 20:54 UTC
Update - Tests have all passed and the updates to the contact has been staged on Aragon.

The next update will be when the votes are enacted in approximately 18 hours.

Sep 14, 19:57 UTC
Update - The fix has been written and is undergoing testing over the next few hours.

Once these tests have passed and the updated contracts reviewed they will be staged on Aragon. Once enacted final tests on mainnet will be conducted and if successful the contract will be unpaused and protocol use will restart.

Current estimated time for restarting the protocol is 36 hours from now (2100 UTC Thursday 15th September).

Sep 14, 09:54 UTC
Identified - We have reviewed the report into the potential vulnerability on one of the periphery contracts and can confirm the vulnerability.

Pausing the contracts means that there is no longer risk of exploitation.

A fix for the issue is being worked on now and will be tested once completed. Once the tests have passed the updates will be staged and deployed and the protocol will be re-activated.

Full postmortem will be annouced after the contracts are re-activated.

Sep 13, 21:32 UTC
Investigating - NFTX protocol is paused while we investigate a report into a potential vulnerability on a periphery contract.
Sep 13, 19:18 UTC
Sep 14, 2022
Sep 13, 2022