baz
Book a demo

Status

8 components over 90 days. The API row is a real request from your browser, not a colour we set when the page was built — and every incident below has its full timeline rather than a one-line summary.

Loading current status…

Scheduled

Every incident, in full

Including the one we would rather not have written up.

  1. INC-118

    Arabic extraction failing silently on scanned pages

    22 July 2026 · 35h 40m

    A change to the extraction pipeline caused scanned Arabic pages to return empty text rather than an error. Documents appeared to index successfully and were absent from retrieval. This is the worst failure mode we have had, because nothing looked wrong.

    1. 22 Jul, 06:40 Investigating A customer reported that a known clause was not being found in a scanned annex.
    2. 22 Jul, 09:15 Identified Scanned Arabic pages have been returning empty text since a pipeline change on 20 July. Affected pages were counted as indexed.
    3. 23 Jul, 14:00 Monitoring Fix deployed and every document ingested since 20 July has been re-processed. Affected customers have been told which matters were involved.
    4. 23 Jul, 18:20 Resolved Re-indexing complete. Extraction now fails loudly: a page that cannot be read is flagged on the matter rather than silently skipped.
  2. INC-121

    Answers slow, and some timed out

    14 August 2026 · 2h 45m

    Inference capacity in the region was saturated for just under three hours. Questions either took far longer than usual or returned a timeout. No answer was returned without its citations.

    1. 14 Aug, 11:05 Investigating Elevated response times on the assistant.
    2. 14 Aug, 11:40 Identified Capacity saturation in the region. Requests are queuing rather than failing.
    3. 14 Aug, 13:50 Resolved Capacity restored. Additional headroom provisioned in the same region — moving load out of the Kingdom was not considered.
  3. INC-124

    Booking confirmations delayed

    29 August 2026 · 1h 35m

    Confirmation emails queued for up to ninety minutes. Bookings themselves were created correctly and no slot was lost or double-booked.

    1. 29 Aug, 08:30 Identified Mail delivery backed up behind a provider-side queue.
    2. 29 Aug, 10:05 Resolved Queue drained and all confirmations delivered.

Why INC-118 is on this page

It ran for 36 hours and nothing looked wrong the entire time. Scanned Arabic pages returned empty text instead of an error, so documents reported as indexed and were simply absent from every answer. A customer found it, not us.

A silent failure in a retrieval system is the worst class of bug we can have, because the product's whole claim is that an answer is grounded in the documents. Extraction now fails loudly and unreadable pages are flagged against the matter — which is the fix, and the write-up stays here regardless.

Security and residency