BINK system status
Live health information for the systems that power BINK, read from the API’s own health checks.
Checking status
Contacting the BINK health checks…
- Last checked
- —
- Source
- API health checks
- Checks
- 9 services
- Re-check
- Every 60 seconds
Core
The checks that gate whether the API accepts requests.
- APIREST endpoints under /api/v1Unknown
- DatabasePrimary datastoreUnknown
- Background jobsQueued work such as deliveries and scheduled runsUnknown
Platform services
Reported by the API as healthy, degraded or critical.
- SettlementPayout and settlement processingUnknown
- Currency exchangeFX quotes and conversionUnknown
- Identity verificationKYC review pipelineUnknown
- NotificationsEmail and push deliveryUnknown
- LedgerDouble-entry postingUnknown
- ReconciliationScheduled reconciliation runsUnknown
Incident history
Resolved incidents, newest first.
No incidents recorded.
Incident history will appear here when recorded. This page currently shows live state only.
How status is determined
This page calls two public health endpoints on the BINK API: a liveness check that confirms the API process is up, and a dependency check that reports each service as up, degraded or down. It re-checks every minute while open.
Operational means the service answered its last check normally. Degraded means it is up but running with reduced capacity. Disrupted means it failed its check. Unknown means the check could not be read.
Status reflects the API as a whole, not your account. Sandbox and production share the same service.
If you are seeing an issue.
The reference, the sandbox and the rest of the developer surfaces — and the error reference for the request ID on any failing response.