Imagine Public API Incident
Affected: Public API
Timeline · 1 update
- investigating Jun 15, 2026, 06:46 PM UTC
We're currently investigating an issue with Imagine: Public API
K3 Imagine Outage History
K3 Imagine is up right nowK3 Imagine had 4 outages in the last 2 years totaling 3h 32m of downtime — averaging 0.2 incidents per month.
There were 4 K3 Imagine outages since November 18, 2025 totaling 3h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
Retalia Performance Degraded
Affected: PortalPublic APIPOSSQL
Timeline · 3 updates
- monitoring Jun 15, 2026, 07:00 AM UTC
Following the identification of severe platform performance degradation, we traced the issue to the queries powering the at-a-glance KPI section of the Portal dashboard. To restore platform stability, the KPI section has been disabled. The remainder of the Portal remains fully available. There are currently no plans to re-enable this functionality until a redesigned solution has been implemented and successfully passed load and performance testing.
- resolved Jun 15, 2026, 09:47 AM UTC
This incident has been resolved.
- resolved Jun 15, 2026, 09:49 AM UTC
We traced the issue to the queries powering the at-a-glance KPI section of the Portal dashboard. The KPI section has been disabled. There are currently no plans to re-enable this functionality until a redesigned solution has been implemented and successfully passed load and performance testing.
Test
Cloudflare Outage
Timeline · 1 update
- resolved Nov 18, 2025, 11:30 AM UTC
Type: Incident Duration: 2 hours and 54 minutes Affected Components: TOP, Portal, POP, Public API, POS Nov 18, 11:30:00 GMT+0 - Investigating - Our platform relies on Cloudflare for DNS and edge network delivery. During the referenced Cloudflare incident, Cloudflare experienced a global network issue that caused requests to our domain to fail before reaching our infrastructure. Our internal systems remained healthy and fully operational, but due to Cloudflare’s network degradation, end-users were unable to reach our service for the duration of the outage. Nov 18, 14:24:09 GMT+0 - Resolved - This incident has been resolved.