All systems operational.

• Marketing site (home)

  Public marketing surface.

  Operational
  90 days ago99.86 % uptimeToday
• Auth

  Login, registration, OAuth, sessions.

  Operational
  90 days ago99.44 % uptimeToday
• HQ Wealth

  Portfolio app, transaction ingest, tax exports.

  Operational
  90 days ago99.58 % uptimeToday
• HQ Docs

  Documentation platform, agent API.

  Operational
  90 days ago99.58 % uptimeToday
• Public docs API

  Read-only documentation + agent API.

  Operational
  90 days ago99.72 % uptimeToday
• Admin

  Staff-only administration.

  Operational
  90 days ago99.31 % uptimeToday

Past incidents

• Elevated error rates on transaction ingest

  Resolved
  2026-04-22 | 13:05 UTC+7 · HQ Wealth · Resolved in 47 min

  A schema migration on the ingest queue introduced a lock that backed up CSV and exchange imports. We rolled the migration forward with a non-blocking index build and drained the backlog. No data was lost; queued imports completed automatically once the lock cleared.

• Intermittent login timeouts

  Resolved
  2026-03-11 | 09:40 UTC+7 · Auth · Resolved in 1 h 12 min

  A session-store connection pool exhausted under a burst of sign-ins, causing a fraction of logins to time out and retry. We raised the pool ceiling and added back-pressure on the token endpoint. Sessions already established were unaffected.

• Documentation API returning stale pages

  Resolved
  2026-02-03 | 17:20 UTC+7 · HQ Docs · Public docs API · Resolved in 2 h 05 min

  A CDN cache key change served previously rendered pages after content updates. We purged the affected paths and corrected the cache key to include the content revision. Live editing in HQ Docs was unaffected throughout.

Incidents older than 90 days roll off this view. Each entry carries a short post-mortem summary; full timelines are kept internally.

How we communicate during an incident

During an active incident, this page is updated within 15 minutes of detection with the affected service, the impact, the current mitigation step, and the next-update time. After resolution we publish a post-mortem with timeline, root cause, and remediation.

For personal-data breaches, we additionally notify affected users and the relevant supervisory authority within 72 hours per GDPR Article 33 and equivalent rules — see the Security page's incident-response section.