saqr

Status

Platform status

Ninety days of history, every incident written up afterwards, and no quiet edits. If we broke it, it is on this page.

Loading current status…

Scheduled maintenance

Video pipeline storage migration

Friday 28 August, 01:00–04:00 (Asia/Riyadh)

Clip retrieval may take longer than usual for up to three hours. Recording and upload are unaffected — nothing stops being captured.

Video pipeline

Incident history

Every incident that affected customers, with what we knew when. Post-hoc edits are not made — updates are appended, including the ones where our first guess was wrong.

Delayed position updates in the Eastern Province

Degraded
Started
2 Aug 2026, 08:40
Duration
47 min
Affected
Tracking ingest
Reference
INC-2026-014

Units on one mobile carrier buffered normally but backfilled slowly, so live positions in the Eastern Province ran up to twelve minutes behind. No data was lost — every buffered position arrived and trip replays for the window are complete.

  1. Investigating 08:40

    Elevated ingest latency on one carrier's range. Investigating.

  2. Identified 08:58

    A routing change at the carrier was fragmenting our backfill batches. Rerouting through the secondary path.

  3. Monitoring 09:14

    Latency back to normal and the backlog is draining. Monitoring the drain rate.

  4. Resolved 09:27

    Backlog cleared. All buffered positions are in and replays for the window are complete.

Video upload backlog

Degraded
Started
15 Jul 2026, 14:05
Duration
3h 20m
Affected
Video pipeline
Reference
INC-2026-011

Clips requested from the incident centre queued behind an unusually large overnight upload batch. Footage was never at risk; retrieval took minutes rather than seconds.

  1. Investigating 14:05

    Clip retrieval is slower than normal. Looking into the queue depth.

  2. Identified 14:41

    An overnight batch from a large fleet saturated the transcoding workers. Adding capacity.

  3. Monitoring 16:20

    Queue is draining steadily. New requests are being served at normal speed.

  4. Resolved 17:25

    Backlog cleared. We have raised the standing worker floor so an overnight batch cannot crowd out live requests again.

Wasl submissions rejected

Outage
Started
3 Jun 2026, 10:15
Duration
2h 12m
Affected
Wasl integration
Reference
INC-2026-009

New vehicle registrations to Wasl failed for just over two hours after an upstream schema change. Existing registrations and reporting were unaffected; queued submissions were replayed automatically.

  1. Investigating 10:15

    Wasl registration submissions are returning errors. Investigating.

  2. Identified 10:44

    An upstream field became mandatory without notice. Patching our payload and queueing submissions meanwhile.

  3. Monitoring 12:02

    Patch deployed, queued submissions replaying.

  4. Resolved 12:27

    All queued registrations submitted and confirmed. No customer action needed.

Dashboard slow to load

Degraded
Started
28 May 2026, 09:30
Duration
1h 05m
Affected
Dashboard
Reference
INC-2026-007

First load of the fleet map took up to twenty seconds for accounts with more than a thousand vehicles. Tracking, alerting and the API were unaffected throughout.

  1. Investigating 09:30

    Reports of slow dashboard loads on large accounts.

  2. Identified 09:52

    A query behind the vehicle list stopped using its index after a migration. Rolling back.

  3. Resolved 10:35

    Rolled back and load times are normal. The migration will go out again with the index in place.

Get told, rather than checking

Incidents that affect your account are pushed to your admin contacts automatically — there is nothing to subscribe to and no separate list to remember to join.

Something wrong we have not caught?

Tell us before we notice. A vehicle reference and a rough time is enough to start from.