Kabeen incident

Data from the Kabeen browser extension partially not recorded

Minor Resolved View vendor source →

Kabeen experienced a minor incident on October 17, 2026 affecting Current status by service (Kabeen web application) and Current status by service (API Kabeen) and 1 more component, lasting 1d 15h. The incident has been resolved; the full update timeline is below.

Started
Oct 17, 2026, 08:22 PM UTC
Resolved
Oct 19, 2026, 11:50 AM UTC
Duration
1d 15h
Detected by Pingoru
Oct 17, 2026, 08:22 PM UTC

Affected components

Current status by service (Kabeen web application)Current status by service (API Kabeen)Current status by service (Web application)Current status by service (Data collection)

Update timeline

  1. investigating Oct 17, 2026, 08:22 PM UTC

    Following a planned update of our platform, some dashboards fail to load and data sent by the Kabeen browser extension is not being recorded.

  2. resolved Oct 19, 2026, 11:50 AM UTC

    The issue is resolved. Data from the browser extension has been recorded normally since Monday, October 19 at 13:50 (Paris time). Impact (Saturday, October 17, 22:25 to Monday, October 19, 13:50, Paris time): - Web application availability checks and page performance measurements collected by the browser extension during this period were not recorded and cannot be recovered. Availability and performance charts will show a gap for this period. - Application sign-in events and time spent in applications were kept by the extension and recorded once the service was restored. - Web application usage (visited applications) was not affected. Cause: a configuration issue introduced during a planned update of our platform prevented some of our services from reaching our measurement database. Most services were corrected on Saturday evening; the service receiving browser extension data was corrected on Monday. Next steps: we have planned improvements so that the browser extension keeps and resends this data whenever our service is temporarily unavailable, and so that our platform queues it before recording it. We are also reviewing how we monitor this service so that such an issue is detected within minutes. We apologize for the inconvenience.