biofrq

status

BioFRQ status.

Real-time health for the face recognition API, the dashboard, authentication, and the marketing site. Last 365 days of uptime and every incident, summarised below.

All systems operational

99.97% uptime · 365 days · 7 incidents · last checked May 24, 2026, 2:20 PM UTC

Services

Face Recognition API

POST /v1/face/execute — detect, liveness, verify, identify, enroll, analyze.

api.biofrq.com

30 d
100.00%
90 d
100.00%
365 d
99.99%

Dashboard

Account management, billing, usage, API keys.

dash.biofrq.com

30 d
100.00%
90 d
99.99%
365 d
99.99%

Marketing Site & Docs

biofrq.com — public site and developer documentation.

biofrq.com

30 d
100.00%
90 d
99.98%
365 d
99.98%

Authentication

Login, session management, 2FA, OAuth.

auth.biofrq.com

30 d
99.95%
90 d
99.98%
365 d
99.98%

365-day uptime

Each cell is one day. The brand accent runs from minor blip to perfect uptime; deeper green = healthier day. Outages tip into red.

99.97% uptime · 7 incidentsLessMore

Recent incidents

  • minor

    May 12, 2026, 8:14 AM UTC

    duration · 27 min

    affected · api

    Elevated latency on identify against large galleries

    A misconfigured pgvector index on a single shard pushed P95 latency on identify above 1.2 s for galleries over 50 k subjects. Index rebuilt; latency returned to baseline within 27 minutes.

  • minor

    Apr 22, 2026, 1:02 PM UTC

    duration · 53 min

    affected · dashboard, auth

    Brief dashboard outage during Supabase upgrade

    Planned Supabase upgrade overran the maintenance window by 53 minutes. Login attempts during the window returned 503. API traffic was unaffected.

  • major

    Mar 8, 2026, 10:30 PM UTC

    duration · 48 min

    affected · api, dashboard, marketing

    Cloudflare edge incident — region: ap-southeast

    Upstream incident at Cloudflare's Singapore POP intermittently dropped traffic from APAC clients. Mitigated by failing over to alternate POPs; restored when Cloudflare resolved upstream.

    read post-mortem →

Stay informed

Subscribe to incident notifications by email, or pull updates into your own monitor.

About this page

Uptime is measured from external probes hitting each public endpoint every 60 seconds from four geographic regions. A day is counted as degraded if any probe sees more than 0.1% failed responses or P95 latency exceeds the published target.

Probe regions · Frankfurt · Ashburn · Singapore · São Paulo