Squash system status

Current service status

This page gives customers and prospects a clear public view of Squash service availability. Squash monitors production infrastructure, application health, authentication paths, and customer-authorized integrations through internal operations tooling.

• Public website

  Operational. The public Squash website, security page, privacy policy, terms, blog, and documentation hub are available at squash.ai.

• Squash application

  Operational. The production application is available to authorized users at app.usesquash.ai.

• API and backend workers

  Operational. Customer workflows, ticket context retrieval, automation planning, and background workers are monitored for health and error signals.

• Authentication

  Operational. Customer and admin login paths use managed authentication and access controls.

• Customer-authorized integrations

  Operational. PSA, identity, documentation, RMM, and communication integrations depend on customer configuration and upstream provider availability.

• Support

  Operational. Customers can reach Squash support at support@squash.ai for incident reports, service questions, and production-impacting issues.

Incident severity and communication

When Squash identifies a production-impacting issue, engineering triages severity based on customer impact, data sensitivity, affected systems, and availability of a workaround.

• Critical incident

  A broad production outage, security-sensitive event, or customer-data risk that requires immediate engineering response and leadership awareness.

• Major degradation

  A customer-facing workflow is degraded or unavailable for one or more customers, but core service access or a workaround may remain available.

• Minor degradation

  A contained issue affects a narrow feature, integration, or non-critical workflow and is handled through normal engineering triage.

• Maintenance

  Planned maintenance is communicated when it is expected to affect customer-facing availability or normal customer workflows.

Response process

Squash uses its incident response process to confirm impact, assign owners, contain the issue, communicate as needed, recover service, and complete follow-up review.

• Detect and confirm

  Engineering reviews alerts, logs, customer reports, and provider signals to confirm whether there is a real customer-impacting event.

• Triage and assign

  An owner coordinates technical response, customer communication, and follow-up actions until the incident is resolved.

• Communicate

  Squash uses direct customer communication, support updates, or public status updates based on incident scope and customer impact.

• Recover and review

  After recovery, Squash records the timeline, root cause or contributing factors, corrective actions, and any prevention work.

Report an issue

For production-impacting issues, email support@squash.ai with the affected workspace, user or tenant context, approximate time, screenshots if safe to share, and a short description of the behavior.

For security concerns, responsible disclosure, or vendor security review, contact security@squash.ai.