Our promise on uptime
HiBFF commits to a target service availability of 99.9% per calendar month for the production hibff.com platform and API. That's a maximum of about 43 minutes of downtime per month.
Target SLO
99.9%
Right now
Healthy
DB ping
2.71ms
What's in scope
- · The hibff.com production website (excluding cached marketing pages served by Cloudflare)
- · All /api/* endpoints on the production API
- · The HiBFF Android app — including OTA updates served via Capgo
- · Authentication flows: email + password, Google OAuth, WebAuthn admin login
- · Crisis safety routing (priority infrastructure — separate, stricter targets enforced internally)
What's out of scope
- · Scheduled maintenance windows (announced ≥ 48 hours in advance via the status page)
- · Outages caused by upstream subprocessors when they breach their own SLAs (we credit you anyway — see below)
- · Force-majeure events including DNS-level attacks against shared infrastructure
- · Issues caused by the customer's own integration code, custom DNS, or local network
How we measure
Availability is measured from /api/health — the same endpoint used by our load balancer. A request counts as "available" if it returns HTTP 200 within 5 seconds and the database ping inside the response is non-null.
External monitors (UptimeRobot, Pingdom-style) sample the endpoint every 60 seconds from multiple regions. Monthly availability = (total_minutes - failed_minutes) / total_minutes × 100.
Service credits (B2B Plus contracts)
If we miss the 99.9% target in a calendar month, customers on a paid B2B Plus contract receive a credit toward the next month's invoice:
| Monthly availability | Service credit |
|---|---|
| ≥ 99.9 % | No credit (within target) |
| 99.0 % – 99.89 % | 10 % of monthly fee |
| 95.0 % – 98.99 % | 25 % of monthly fee |
| < 95.0 % | 50 % of monthly fee |
Credits are claimed within 30 days of the affected month by emailing business@hibff.com with the customer ID and relevant period. Credits do not exceed the customer's monthly fee.
Incidents & postmortems
Every WARN+ event is recorded on our public status page. For incidents that breach the SLO, we publish a postmortem within 7 business days covering: what happened, when, root cause, immediate fix, follow-up actions, and any process changes.
Need this in a signed agreement?
We provide a tailored SLA + Data Processing Agreement to every B2B Plus customer.
business@hibff.comSLA last reviewed: 25 April 2026. Live status