Status and incidents
How you find out when Divvent or your application has a problem, what we email you about, and how to reach us.
When something goes wrong, you want to know whether it is your application, Divvent, or the hosting underneath both, and whether anyone is already on it. This article covers what Divvent tells you today, where to look, and how to reach us.
There is no public status page yet
Divvent does not have a public status page yet. For now, the place to look for your own application is its Health tab, and the emails below.
Check your application's Health tab
Open your application, then Settings, then Health. It shows:
- how your application has done over the last day: requests, failures, refusals and the slowest screens;
- What went wrong, with Ask why beside each item, so the AI can tell you the likely cause;
- Incidents: anything unusual Divvent noticed, whether it is open or resolved, and whose it most likely is.
The article Health and Activity explains every part of the tab.
How Divvent watches for problems
Every hour, Divvent looks at each application's numbers: counts, error kinds and timings, never its records. It compares them with the application's own recent history and opens an incident when something stands out, for example:
- a new kind of failure;
- more failures, or more refusals, than usual;
- a step in a flow failing;
- screens becoming slower than usual;
- the application reporting as unhealthy after a release.
Before anything else, it works out whose problem it most likely is:
| Shown as | Means |
|---|---|
| the provider's | The hosting provider, or a service your application connects to, had a problem. Not your application and not Divvent |
| the platform's | Something in Divvent's own platform. Ours to fix |
| the application's | Something in your application, or its latest change |
| not yet known | Nothing yet tells these apart |
When it is your application or the platform, Divvent asks the AI for the likely cause, and our team looks at what it suggests. If a change to your application would stop it happening again, that change comes to you for review, like any other; nothing is changed without approval. See Read a change and approve it.
When the hosting provider has a problem, Divvent also holds back platform updates until it is over. See Platform updates.
An incident closes by itself once the numbers are back to normal.
Emails you may get
| Sent to | When | |
|---|---|---|
| An incident is over | Your account's owners | After an incident is resolved, if your setting says so. By default, only when it reached your users |
| Storage nearly full | Your account's owners | Once, when an application's database reaches 80% of its limit |
| Support access | Your account's owners | When someone on our team is approved to look at how your application is running |
Incident emails. You choose when your account hears about an incident on the Health tab, under Tell this account about an incident, after it is over: only when it reached our users, every time or never. Owners and admins can change it. The email says when the problem started and ended, whether it was the hosting provider, the Divvent platform or your application, and that it is resolved. If a change would prevent it, the email says it is waiting for your review.
Storage emails. The email names the application and how full its database is. It does not name any of your records or tables. Nothing is wrong yet at that point: when a database is full, new records cannot be saved until space is freed or the limit is raised, so the email comes while there is still time to choose. Reply to it and we will raise the limit or help you work out what is taking the room.
Support access emails. These say who has access, who approved it, why, what they can look at and until when. See Security, and what Divvent can and can't see.
If something looks wrong and nothing has told you
- Open the application's Health tab and look at What went wrong and Incidents.
- If a failure is listed, press Ask why for the likely cause.
- Check Activity for a recent release or change that lines up with when it started. If a release caused it, you can go back to the version before. See Roll back a release.
- If you are still stuck, email us.
If the portal itself shows "Something went wrong on our side, and it is ours to fix", try again in a few minutes. If it keeps happening, email us.
Contact us
- Anything at all: hello@divvent.co.uk.
- A security problem: security@divvent.co.uk. Our disclosure policy is at divvent.co.uk/security, and the site publishes a security contact file at divvent.co.uk/.well-known/security.txt. We reply within three working days to say we have your report, and tell you what we are doing about it within ten.
If a personal data breach ever affects your data, our data processing agreement commits us to tell you without undue delay, and within 48 hours of becoming aware of it. See Terms, privacy and your data processing agreement.