All Systems Operational

Uptime over the past 90 days. View historical uptime.
app.salv.com Operational
90 days ago
99.99 % uptime
Today
demo.salv.com Operational
90 days ago
100.0 % uptime
Today
salv.com Operational
90 days ago
100.0 % uptime
Today
API docs Operational
90 days ago
100.0 % uptime
Today
bridge.salv.com Operational
90 days ago
100.0 % uptime
Today
bridge-demo.salv.com Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 28, 2026

No incidents reported today.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

Jun 24, 2026

No incidents reported.

Jun 23, 2026

No incidents reported.

Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026

No incidents reported.

Jun 18, 2026
Database migration - brief Salv API disruption
Completed - The scheduled maintenance has been completed.
Jun 18, 02:35 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 02:05 UTC
Scheduled - We're scheduling a maintenance window to finalize an ongoing database migration on the Salv platform. During the window the Salv API may intermittently return 5xx errors (typically HTTP 503 / 500) while a small set of tables are locked for a final schema change.

Expected disruption:
A few minutes within this window; the full window is reserved as a safety buffer.

Impact
API endpoints that read or write transactions, persons, or sanction alerts may briefly fail. In particular:

• Persons
POST/GET/PUT /v1/persons, POST/PATCH /v2/persons,
GET /v1/persons/{personId}

• Transactions
POST/GET/PUT /v1/persons/{personId}/transactions(/{id})
GET /v1/persons/{personId}/transactions-summary

• Sanction & screening alerts
GET /v1/sanction-alerts
GET /v1/sanctions/alerts/{id}
GET /v2/sanctions/alerts/{id}/related-alerts
GET /v1/screening-alerts/{id}/hits
GET /v1/persons/{id}/screening-checks
GET /v1/transactions/{id}/screening-checks

• Monitoring
GET /v1/persons/{id}/monitoring-checks
GET /v1/transactions/{id}/monitoring-checks

• Bulk ingest
POST /v1/data-upload
GET /v1/data-upload/{uploadId}/status

• Manual alerts
GET/POST/PUT /v1/manual-alerts(/{id})

Other endpoints (cases, rules configuration, lookups, etc.) are not expected to be affected.

What to expect
- Requests to the endpoints above may fail with 5xx for short periods during the window.
- No data will be lost. Once the migration completes, all endpoints return to normal behaviour.
- We recommend pausing non-critical batch ingest jobs (POST /v1/data-upload) for the duration of the window, and ensuring your integrations retry 5xx responses with exponential backoff.

What you don't need to do
- No changes to your integration or credentials are required.
- Response shapes and field types in the API stay the same.

If you have any questions or need to coordinate the timing, please reach out to your Salv contact.

Thanks,
The Salv team
Jun 4, 13:23 UTC
Jun 17, 2026

No incidents reported.

Jun 16, 2026

No incidents reported.

Jun 15, 2026

No incidents reported.

Jun 14, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage