Client websites independent check failed
The independent check failed twice. This indicates a monitored delivery problem, but does not by itself confirm that every customer function is unavailable.
At least one service is reporting an outage. Other services may still be available; check each component below.
Public website reachability and content. HTTP 200: the public pre-launch page is being served.
The count of customer websites is not deployed on the live API yet. Test site and its custom domain checked independently: expected content not confirmed.
Sign-in API refuses an unauthenticated request correctly; editing and publishing are not exercised. HTTP 401 and expected content confirmed.
Price list, card payments (Stripe and Paddle) and the domain registrar each answer a read-only question; no payment or registration is made. Every part answered.
Mail server accepts IMAP and SMTP connections and greets correctly; delivery of an individual message is not tested.
Chat knowledge service responds; the quality of an individual answer is not tested. HTTP 200 and expected content confirmed.
Public API health endpoint; not every API operation. HTTP 200 and expected content confirmed.
Webmail front door content; not mailbox or SMTP delivery. HTTP 200 and expected content confirmed.
Client website delivery: Offline. Every published client website is opened the way a visitor would open it, at its fastsites.app address and at any custom domain, and counted only if its own content loads. The counts are in the Client websites line above.
Your published site, the editor and your email are separate services. A problem in one does not automatically mean the others are down. Cloudflare’s network status is useful context, but does not confirm that a particular website is working.
Report a website issue Cloudflare network statusThe independent check failed twice. This indicates a monitored delivery problem, but does not by itself confirm that every customer function is unavailable.
No planned maintenance reported in the current feed.
Something not working on your own site?
Contact supportWe use cookies
We use essential cookies to make our site work, and optional ones to understand how it’s used so we can improve it. You can accept or decline the optional ones. Learn more.