Skip to content
Book demoStart free

Resources · Status

All systems operational

Live service health, 90-day uptime, and a full incident history. Updated automatically — no marketing team in the loop.

All systems operationalUpdated 30s ago

Services

Current health, with 90-day uptime.

99.95% SLA
  • Web app
    litehq.com dashboard, operator + member portals
    Operational
    90-day uptime99.992%
  • API
    REST API, public + internal endpoints
    Operational
    90-day uptime99.987%
  • Stripe Connect
    Card, ACH and direct-debit charge pipeline
    Operational
    90-day uptime99.974%
  • Xero sync
    Invoice + payment reconciliation cron
    Operational
    90-day uptime99.948%
  • Magic-link emails
    Auth and visitor magic-link delivery
    Operational
    90-day uptime99.961%
  • Booking engine
    Room + desk reservations, capacity checks
    Operational
    90-day uptime99.983%

Uptime is measured as successful health-check responses against external probes from three regions. SLA credits, where applicable, are calculated on the monthly rather than 90-day window.

Incident history

The last four incidents, in full.

Every incident is publicly post-mortemed within 7 days. We list duration, impact, and root cause — not just the green-light.

Full archive
  1. May 18, 2026
    Resolved38 minXero sync

    Xero sync delayed for 38 minutes during NZ business hours

    Impact

    Invoice sync to Xero lagged for approximately 1,200 in-flight invoices; no member-facing degradation. All invoices reconciled automatically once sync resumed.

    Root cause

    An upstream Xero OAuth token-refresh endpoint returned 503s during a partner-side incident window. Our refresh-with-backoff retried and recovered without intervention; we have since adjusted the alert threshold so the on-call gets paged at 5 minutes of consecutive failures rather than 15.

  2. May 5, 2026
    Resolved14 minMagic-link emails

    Magic-link email delivery delayed via secondary SMTP relay

    Impact

    Approximately 480 magic-link emails were delayed by up to 9 minutes. New logins fell back to password auth where configured; no failed logins.

    Root cause

    A regional outage at our secondary SMTP relay caused us to drain queue traffic through the primary, which briefly exceeded its rate limit. We have since rebalanced the relay weights and raised the primary’s daily quota with the provider.

  3. Apr 22, 2026
    Resolved6 minAPI

    API 502 errors on /bookings list endpoint

    Impact

    Roughly 3% of /bookings list calls returned 502 for six minutes during the incident window. Booking creation and member portal flows were unaffected.

    Root cause

    A new Postgres index was building on production behind a CONCURRENTLY flag, and a long-running planner cache invalidation caused a brief spike in 502s on the read replica. The index built successfully; we now stage CONCURRENTLY index builds in a maintenance window with read-replica preheat.

  4. Apr 9, 2026
    Resolved22 minStripe Connect

    Stripe Connect webhook backlog after platform-side incident

    Impact

    Booking confirmation emails for paid checkouts were delayed by up to 14 minutes. All bookings ultimately confirmed via the scheduler self-heal pipeline; zero double-charges.

    Root cause

    Stripe’s Connect webhook delivery was paused platform-wide for 18 minutes. Our 4-layer payment confirmation pipeline absorbed the backlog without operator intervention; we have since added a synthetic webhook replay to our weekly disaster-recovery drill.

Subscribe

Get incident updates by email.

One email when an incident opens, one when it resolves. No marketing, no roadmap teasers. Unsubscribe in one click.

Status JSON feedRSS availableSLA report on request