STATUS · LIVE

All systems nominal. Observed in real time.

EasyLiveChat continuously probes each component of the platform. This page is a live read on the same checks that drive our internal alerting — no marketing fluff, no delayed sync.

CHECKED EVERY 30sAll systems nominal

API

API gateway

Operational

Hono + Bun REST surface. All /api routes flow through this tier.

LAST 90 DAYSChecked 4:31:14 PM
90d agotoday

DB

Postgres primary

Operational

Tenant-isolated Postgres 16, eu-central-1 primary with hot standby in eu-west-1.

LAST 90 DAYS74 ms probe
90d agotoday

CACHE

Redis cache

Operational

Redis 7 — pub/sub, rate-limit, presence, edge-cache backing store.

LAST 90 DAYS2 ms probe
90d agotoday

WS

Socket.IO

Operational

/agents and /widgets namespaces, Redis adapter for horizontal scaling.

LAST 90 DAYSEngine reachable
90d agotoday

EDGE

Edge proxy

Operational

L1+L2 cached tenant lookup, TLS termination, custom-domain ACME.

LAST 90 DAYSDerived from API reachability
90d agotoday

CDN

Widget CDN

Operational

cdn.EasyLiveChat.com — the embeddable widget loader & locale dictionaries.

LAST 90 DAYSCloudflare edge — all PoPs nominal
90d agotoday

LEGEND

OperationalDegradedDownUnknown

REGION

eu-central-1 · Frankfurt (primary)

eu-west-1 · Dublin (warm standby)

RECENT

Incidents we've written up.

See full release history →
  1. Elevated WhatsApp egress latency in eu-central-1

    Meta's upstream returned 503s on roughly 4% of WhatsApp outbound requests for 33 minutes. No customer messages were lost; affected messages were retried automatically once the upstream recovered.

    MINOR
  2. Database read replica promotion

    During a routine Postgres maintenance window, read traffic briefly failed over to a stand-by replica. P95 read latency rose to 380ms for 8 minutes; the primary was reattached without incident.

    MINOR
  3. Socket.IO reconnect storm after Redis adapter restart

    A scheduled Redis upgrade caused the Socket.IO Redis adapter to drop all live sessions simultaneously. Connections reconnected automatically; the reconnect storm caused brief queue back-pressure. Mitigation: staggered reconnect jitter added in v0.9.2.

    MAJOR

For real-time incident updates, subscribe at status-subscribe@livechattools.com.