Use the Hatz status page to check whether there is an active incident or degraded service: https://status.hatz.ai.

During an active incident, the status page is the source of truth for current status and updates. A support ticket can still be useful when Hatz needs to understand account-specific impact or confirm whether your symptoms match the posted incident.

If a support ticket is needed during an active incident, include affected tenants or users, product area, timing, symptoms, scope, screenshots or errors, whether there is a workaround, and whether the issue matches the posted incident.

If the status page does not show an active incident, open the support request around the actual symptom first, such as Bug / Product Issue, Workshop Help, Integrations, API / Developer, Files / Exports, Account Access, Credits / Usage, or General Questions.

Hatz can still investigate if evidence suggests a broader incident. If an incident is later confirmed, the ticket can be linked to the incident response.

Some customers report symptoms before an incident is formally posted or after an incident is marked resolved. Those tickets should capture the same evidence packet and note the timing relative to the status page update.

If the customer is still affected after a posted incident is resolved, create or continue a structured support ticket so Support can investigate the account-specific impact.