If you have ever had a crypto app's website fail to load, show the wrong balance, or hang on "loading" forever, the first instinct is often panic. It feels like your money just disappeared. In almost every case, nothing of the sort happened. What broke was a website. Your funds, if you hold them in a self-custody wallet, live somewhere else entirely.
This guide walks through what a dapp frontend actually is, what it is not, and a real, recent example of this exact situation playing out on Base.
A frontend is a tool for building transactions, not a vault
When you use a swap app, an NFT marketplace, or a lending interface, the website you see is called the frontend. Its job is to give you buttons and fields instead of raw contract calls, and to package your choices into a transaction that it hands to your wallet for you to sign. Once you approve something in your wallet, the transaction goes to the Base network directly. The frontend's part in that specific action is already finished.
Your funds do not sit on that website, in that company's database, or anywhere the frontend's operator controls. They sit in a smart contract or at your own address on Base, and the only thing that can move them is a valid, signed transaction from your wallet. The frontend never holds your keys and never holds your tokens. It is closer to a storefront window than a bank vault. If the storefront closes for the day, the goods behind it have not vanished.
Our guide on self-custody covers this distinction in more depth: in a self-custody wallet, your recovery phrase is what controls your funds, not any particular app, company, or website.
A real example: the October 2025 AWS outage
This is not just a theoretical point. On October 20 and 21, 2025, a major outage in Amazon Web Services' US-EAST-1 region cascaded into Infura, one of the largest providers of the backend connections (RPC endpoints) that wallets and apps use to read blockchain data. MetaMask and other wallets that relied on Infura started showing incorrect balances, in many cases displaying zero for tokens people definitely still owned. Coinbase's Base App was affected the same way for some users. Base's own transaction volume dipped noticeably during the outage before recovering within a couple of days.
Coinbase stated plainly that no user funds were lost in the incident. What failed was the infrastructure that reads and displays data, not the ledger that records who owns what. Base kept producing blocks the entire time. The tokens people thought had disappeared were sitting at the same addresses they always had been, and balances corrected themselves once the underlying services came back online.
This is a useful case study because it separates three things that get lumped together in people's minds: the blockchain itself, the RPC provider that lets an app talk to the blockchain, and the frontend website people actually click around in. Any one of those three can have a bad day without the other two being affected. Our guide on what an RPC endpoint is goes into more detail on that middle layer.
What you can actually do if a frontend is acting up
If a swap app's site will not load, is stuck, or is showing numbers that look wrong, a few steps usually settle things down:
- Check your balance somewhere else. Open a block explorer like Basescan and look up your address directly, or check the balance in your wallet app itself rather than the website. If the explorer and your wallet both show the correct balance, the website is the thing with the problem.
- Wait before acting. An RPC or hosting outage is usually resolved within hours, not days. Resist the urge to move funds urgently in response to a display glitch, since a rushed transaction confirmed under stress is a common way people make costly mistakes.
- Know that open source contracts do not depend on one website. Many dapps on Base are built on smart contracts that anyone can interact with, including through Basescan's own Write Contract tab, which talks to the contract directly without any company's frontend in the loop. This is usually a fallback for advanced cases rather than something you need day to day, but it illustrates why the website and the contract are genuinely separate things.
What this does not protect you from
None of this means every frontend problem is harmless. A frontend going down and a frontend being compromised are different situations with different consequences. If a dapp's website is hacked or DNS hijacked to point at a lookalike domain, the fake site can present you with a transaction that looks normal but does something malicious, and your wallet will faithfully ask you to sign whatever it is told to build. That risk is about verifying you are on the genuine domain and reading what your wallet actually asks you to approve, which is a different problem from an outage. Our guides on typosquatting and lookalike sites and wallet signature requests cover that risk specifically.
The bottom line
A dapp's frontend is a convenience layer sitting on top of the blockchain, not the place where your funds actually live. When a website, an RPC provider, or a company's backend has an outage, as happened across much of the crypto industry during the October 2025 AWS disruption, the usual result is a wrong or missing number on a screen, not a wrong or missing balance on-chain. Knowing the difference between a frontend problem and an actual loss of funds is one of the more reassuring things to understand about holding your own keys.