Reliability · three-year ledger

Uptime history

Every quarter, every service, every incident. The numbers behind the SLO — not a marketing dashboard. Credits issued where the SLO was missed; €0 where it wasn’t.

Quarters tracked

12

API · trailing 3 yr

99.997%

Total incidents

27

SEV-1 in last 24 mo

1

Quarterly ledger

Per service, per quarter

QuarterAPIConsoleIngestWebhooksIncidentsCredits issuedWorst incident
Q2 202699.998%99.997%99.994%99.991%2€0SEV-3 · 14 min ingest lag · Aug 3
Q1 202699.999%99.999%99.997%99.995%1€0SEV-3 · 8 min ingest lag · Feb 11
Q4 202599.996%99.995%99.992%99.988%3€4,180SEV-2 · 38 min console degradation · Nov 22
Q3 202599.998%99.998%99.996%99.993%2€0SEV-3 · 12 min webhook delay · Sep 4
Q2 202599.997%99.996%99.994%99.990%2€0SEV-3 · 18 min ingest lag · May 19
Q1 202599.999%99.998%99.997%99.994%1€0SEV-3 · 6 min API latency spike · Jan 28
Q4 202499.994%99.992%99.988%99.984%4€9,640SEV-1 · 47 min API outage · Dec 7
Q3 202499.997%99.996%99.994%99.991%2€0SEV-3 · 11 min console latency · Aug 22
Q2 202499.996%99.995%99.992%99.989%3€2,140SEV-2 · 26 min webhook outage · Jun 14
Q1 202499.995%99.994%99.991%99.987%2€0SEV-3 · 22 min ingest lag · Mar 8
Q4 202399.993%99.991%99.987%99.982%3€6,820SEV-2 · 41 min API degradation · Oct 30
Q3 202399.996%99.995%99.993%99.990%2€0SEV-3 · 16 min console latency · Jul 11

Measurement: blackbox probes from five independent regions, 30-second cadence, error-budget calculation matches the published SLO methodology.

Where this comes from

The same numbers our on-call rotation closes the day with.

Published on the first business day of each quarter, signed off by the head of SRE and reviewed by the audit committee.