Site monitoring
See whether your published site is up and which crashes real visitors ran into. Volnyn starts a repair build for new crashes on its own.
A site can look fine in your preview and still break for a visitor — on one page, in one browser, after one click. Monitoring shows you those crashes as they happen on the live site, and tries to fix them before you even notice.
Open Monitoring from the More hub in the chat panel, or go to /user/site/monitoring. It works on AI-built sites.
What the page shows
| Card | What it tells you |
|---|---|
| Uptime check | Whether the site is published, with a Check now button. |
| Open crashes | Errors not yet resolved — "Being repaired automatically" or "Nothing outstanding". |
| Distinct errors | How many different errors were recorded (the last 50). |
| Total hits | How many times visitors hit them. |
| Last crash | When the most recent crash happened, or None reported. |
Use Open live site at the top to check the site yourself.
Uptime check
Click Check now to send a live request to your site from Volnyn's server. You get the HTTP status and the response time — for example HTTP 200 in 340 ms. If the site does not answer, you see the error instead.
The check runs when you click it. Publish the site first; an unpublished site has nothing to check.
Runtime errors
Published AI sites report crashes from the visitor's browser the moment they happen — a blank page, a component that failed to load, an error screen. Each one lands in the Runtime errors list.
- Repeats of the same error collapse into one row with a hit counter, so a crash that hit 200 visitors does not bury everything else.
- Each row shows the error, the page, how many hits, when it was last seen, and its repair status.
- The list shows the latest 50 distinct errors.
Automatic repair
When a new crash comes in, Volnyn starts a targeted repair build for that site on its own — broken published sites fix themselves without you opening the chat.
To avoid endless rebuilds, automatic repairs are limited to one every two hours and three per day for each site.
| Status | Meaning |
|---|---|
| dispatched | A repair build was started for this crash. |
| throttled | It repeated too fast, so the repair was held back briefly. |
| busy | Another build was already running; it will be picked up after. |
| failed | The automatic repair could not fix it — ask the AI in chat. |
| resolved | You marked it done. It reappears if it happens again. |
Mark resolved
Click Mark resolved on a row once you are happy it is fixed. It leaves the open list and only comes back if a visitor hits the same error again.
If something is broken right now
Click Ask AI to fix it. It opens chat with a request to find and fix the crash on the affected page. The assistant can read the exact error from this record, so you do not need to copy anything.
You can also describe what you see in your own words — see Editing your site with chat.
FAQ
Is this continuous uptime monitoring?
No. The uptime check runs when you click Check now. Crash reporting, on the other hand, is always on — it comes from real visitors' browsers.
Why is the crash list empty?
Either nothing has broken, or the site has not had visitors since publishing. If the page says "Crash history is being set up", the list is briefly unavailable while automatic repairs keep running.
Do automatic repairs cost me anything?
Repairs are rebuilds of your site. See Plans and credits for how builds and edits are charged, and check Settings → Usage for what was spent.
Does monitoring track visitors?
No. It records errors, not people. For visitor numbers use Project analytics or Google Analytics.
My whole site is down, not just one page.
Run Check now to confirm, then see Why is my website blocked or not loading?