1. Confirm it is offline for everyone
Open your address on your phone with Wi-Fi off, so it uses mobile data, in a private window. If you can ask someone in another place to open it, do that too. If it opens for them, the problem may be your own network or browser.
2. Read what the page says
Some hosts take an app offline for reasons about the account, not the code: used-up credits, a failed payment, or a free-tier published app that has reached the end of its time. Visitors then see a page from the host instead of your app. In public posts from September and October 2026, owners described published apps going offline after credits ran out or a billing change, and after a notice that a published app had expired.
Copy the exact words on the page, or take a screenshot. Support will ask for them.
3. Check your host's status page
Hosts and AI builders usually have a status page that lists known problems. If it shows one, there is nothing to fix on your side. Check again later.
4. Check credits and billing
Sign in to your host's account. Look at your credits, your payment method and any notice about a failed payment. A payment can fail for reasons that have nothing to do with money in your account, for example a card that needs an extra confirmation from your bank.
5. Check your domain and security certificate
If your address is your own domain, check when it renews in your domain provider's account. An expired domain stops your site from opening. An expired security certificate (the file that lets browsers show a padlock) makes browsers show a warning instead of your site.
6. Did you publish just before it went offline?
If it went offline right after you published, ask your AI tool to list what it changed. If your tool lets you go back to the previous version, you can try that. See Supabase paused my project and my app is down. What do I do? for one known case.
What to send to your host's support
- The exact message shown, or a screenshot.
- Your web address.
- The time you first saw the problem, with your time zone.
- What you changed or published just before, if anything.
What Heedza checks, and what it cannot see
Heedza requests your home page on a schedule and alerts you when it stops answering. It tells you the site is down. It does not tell you why. It also reminds you 14, 7, 3 and 1 day before your HTTPS certificate or your domain registration expires.
Heedza cannot see your host's credits, billing or status page, and it does not restart or host your app.
Your next step: run the free scan
Use the free scan at the bottom of this page. Paste your live web address. It opens your home page, looks for secret keys in its code, checks a few private files and looks at what search engines see. No account is needed.