LIVE SERVICE STATUS OPENBANK

A clearer view of what's working.

External checks. Incident history.

Checking service statusConnecting to our independent status checks…
Last checked: —Updated every 2 minutes
Two OpenBank lions and a robot monitoring services
Monitoring live
PUBLIC STATUS · ALL TIMES UTCExplore live checks
01 / LIVE CHECKS

Service status.

Each result covers only the check named below.

Operational Impacted Unverified
◎
◈
↗

Scope: Website, sign-in, API edge. Mobile journeys and payments are not measured here.

02 / HISTORY

Observed availability.

Successful website checks ÷ valid checks. Missing samples stay unverified.

PUBLIC WEBSITE · OBSERVED AVAILABILITY
— awaiting data
Samples observed—
—Now

Availability is calculated from recorded external probe results, not estimated from page views.

03 / INCIDENTS

Incident log.

Confirmed after 3 failed checks; resolved after 2 passes. Times in UTC.

○
Checking incidents
04 / RELIABILITY, DEFINED

Know the difference.

Measurement, target, agreement. Three distinct things.

01 / MEASURED

SLI Indicator

The measured result for a defined service and period.

successful checks ÷ valid checks
02 / TARGET

SLO Objective

An internal target for one SLI and time window.

example: 99.9% over 30 days
03 / CONTRACT

SLA Agreement

A contractual promise with scope and remedies.

examples here are not an SLA
ERROR BUDGET · EXAMPLE

How much downtime?

Allowed unavailable time over 30 days for a hypothetical SLO.

30-DAY BUDGET43m 12s
(1 − 0.999) × 30 × 24 × 60 minutes
◷

Latency · p95

95% of measured requests finish within this time.

↺

RTO · RPO

Target restore time · maximum acceptable data-loss window.

◎

MTTD · MTTR

Measured time to detect · measured time to restore.