Current status
All seven Fluxa components are operational as of the latest check. The full live page with real-time monitoring is at /live; the archive on this page covers everything that has ever stopped working.
Payments APIOperational
Merchant dashboardOperational
Hosted checkoutOperational
Embedded checkout SDKOperational
Webhook deliveryOperational
Settlement processingOperational
Ledger integrityOperational
Historical incidents
No incidents yet
Fluxa is pre-launch. The first incident, when it occurs, will be recorded here with the full timeline, root cause, and corrective action. Until then, the archive is empty.
When an incident does occur, it will appear in this list with:
- Reference · unique
INC-YYYY-NNNN identifier - Affected components · specific Fluxa components impacted (API, dashboard, checkout, webhooks, etc.)
- Timeline · first detection, root cause identified, mitigation applied, resolution confirmed, all timestamped to the second in UTC
- Root cause · what happened, in plain English, after the incident is fully resolved
- Corrective action · what changes have been or will be made to prevent recurrence
- Customer communications · what affected merchants were told and when
Severity classification
Incidents are classified by impact on the merchant-facing service:
- SEV-1
- Critical · payment processing fully unavailable, settlement halted, or data integrity issue affecting completed transactions.
- SEV-2
- High · one or more components degraded, error rates above SLA, or partial unavailability of merchant-facing services.
- SEV-3
- Medium · non-blocking degradation, individual merchant or feature affected, workaround available.
- SEV-4
- Low · scheduled maintenance, informational notices, or issues not affecting live transactions.
Subscribe to updates
You can subscribe to receive incident notifications via three channels. Each channel sends an alert when an incident is created, updated, or resolved:
Programmatic feeds are also available: Atom, RSS, and JSON.