Incidents & uptime
Run SEV1 to SEV4 incidents with a timeline and incident commander, monitor URLs automatically and keep clients updated by email, without a separate status tool.
Checkout returning 502 errorsCommander: Sam Okafor · Linked: deploy v2.4.0
Uptime check on /checkout failed 3 times in a row. Incident opened automatically.
Cause found in v2.4.0 payment timeout setting. Rolling back.
Rolled back to v2.3.9. Client update sent to 4 subscribers.
Five consecutive successful checks. Resolved automatically.
Quick answer
Jonta runs incidents from SEV1 to SEV4 with an incident commander, a timeline and links to the ticket or deployment involved. Uptime checks can open an incident automatically after repeated failures and resolve it when the site recovers, while subscribed clients receive email updates.
Run incidents in the same place as the work that caused or fixes them.
Jonta notices when a site is down and opens the incident for you.
Clients hear about incidents from you first.
Nothing sits forgotten in a column.
Built to be run and monitored properly.
Included on every plan: Free, Pro and Enterprise. See pricing.
For many agencies, no: client-visible incident updates appear in the client portal and subscribed clients receive emails. Jonta does not currently host a public status page for anonymous visitors.
You set the check interval, timeout, expected status code and severity for each monitor. Thirty days of check history are kept.
Try every feature free for up to 5 users.
Free for up to 5 users
Every feature on every plan. £80 a month for up to 50 users after that, and free migration from Jira and Confluence.