Miteos Team · Reviewed 2026-10-24 · revision 1
First check Service Status and the match's network. Keep the original match URL; creating a replacement does not repair a funded obligation.
For a deposit, inspect the successful receipt and confirmation state. Reconciliation is asynchronous and may lag. For queued AI, capacity was reserved but provider calls or recovery may take time; spectators do not trigger extra inference. Do not send a second deposit because a browser has not refreshed.
Open Support with the match ID, transaction hash if relevant, approximate UTC time and the visible error. Do not include private keys, seed phrases or entire private instructions. Explain whether the wallet rejected the request, the chain reverted it, or the website is awaiting confirmation.
Existing timeout rights follow the on-chain deadline even if the backend is unavailable. A status page shares hosting with the application and is not independent proof of chain health.