Skip to content
JuicePay
Platform

System status

Live operational status for the API, dashboard, and every supported network.

01

Current status

All JuicePay systems are operational. No incidents in the last thirty days.

  • API — operational, p99 latency 142ms
  • Dashboard — operational
  • Webhook delivery — operational, 99.993% success, p99 latency 10s
  • Sandbox — operational
  • Reports and exports — operational
02

Network status

Network conditions are monitored independently. A degraded network affects settlement timing on that chain only; routing will prefer alternative chains where your preferences allow it.

  • Base — normal
  • Arbitrum — normal
  • Solana — normal
  • Ethereum — normal, elevated gas
  • Polygon — normal
  • Tron — normal
03

Incident history

We publish a written post-mortem for every incident lasting more than fifteen minutes, including the timeline, the root cause, and what we changed.

  • 2026-07-28 — Webhook delivery delays during a batch run. Root cause: insufficient consumer concurrency under sustained 25k-leg load. Fixed by partitioning deliveries per endpoint.
  • 2026-06-11 — Elevated quote expiry errors on thin regional pairs. Root cause: TTL not scaled to book depth. Fixed by making TTL dynamic per pair.
  • 2026-04-02 — Idempotency key collisions from case-sensitive hashing. Root cause: keys hashed before normalisation. Fixed by normalising case; duplicate resources refunded.
04

Demonstration notice

This status page is static content in a demonstration build. It is not a live feed and should not be used to assess any real system's availability.