Service status
Hooq status
Hooq - Secure Work Item Sync for Jira. Status of the Hooq service and how we communicate incidents.
How this page works: the platform rows below are read live from Atlassian’s public status pages every minute. The Hooq row is derived from those and from the incident list on this page, which we maintain by hand. We do not publish an uptime percentage.
Checking...
Last checked: -. Refreshes every minute.
Atlassian platform (live)
Hooq runs entirely on Atlassian’s Forge platform and calls the Jira Cloud APIs. These rows are read live from Atlassian’s public status pages (developer.status.atlassian.com, jira-software.status.atlassian.com).
| Component | Status | Updated by Atlassian |
|---|---|---|
| Atlassian platform | Checking... | - |
Hooq sync service
| Component | Status | Basis |
|---|---|---|
| Hooq sync service | Depends on the Atlassian Forge platform shown above; no Hooq incidents reported | Derived, not measured. Hooq has no public health probe. The incident list below was last updated 3 October 2026. |
Incidents
No incidents reported. Last updated .
How we handle incidents
We detect problems through monitoring and customer reports, classify them by severity, post an update here for anything that affects customers, fix or mitigate first and then address the root cause, and publish a summary within 10 business days of a resolved incident. If your data is involved we tell you directly within 72 hours of confirming it. The full process is in the Incident Response Plan.
Report a problem or get updates
Response targets: we reply to reports within 3 business days (as in our security policy) and post an update here for anything that affects customers. Email [email protected], or use the support portal linked from the Hooq listing on the Atlassian Marketplace. To be told about incidents by email, send us a message asking to be added; we send updates to everyone on the list when we post one.
Hooq is a product of Limbus Lab.