Kollective had 7 outages in the last 2 years totaling 24h 20m of downtime — averaging 0.3 incidents per month.
There were 7 Kollective outages since June 26, 2025 totaling 24h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is an outage with Cloudflare, preventing access to our geo-steered services. We are investigating the issue.
Cloudflare has implemented a fix, and services are recovering.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Certain events dashboards in the Kollective Portal are failing to load consistently. We are investigating the issue.
The issue has been identified, and a fix is being implemented. Impact is limited to custom dashboards.
A fix has been implemented and we are monitoring the results.
The issue was identified as a bug from our graph/table rendering sub-processor. We are working around the issue, and visualizations should be performing normally at this time.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers using Teams Live events are experiences degraded performance
On June 25th 2025 at 1:59 PM Kollective released KSDK 3.6.3. This release contained refactored code that caused the KSDK to hang when forced to fallback to CDN, preventing playback of a live event. Kollective's development team was alerted at 8:41 PM \(PDT\) of a potential outage. The outage was verified and service was restored at 9:07 PM \(PDT\). The changes to the KSDK were reverted from the testing branch at 2:00PM on June 26th. QA has identified the testing failure as an invalid configuration in the testing environment that allowed for playback despite the configuration settings. Current manual testing steps have been fixed and work is proceeding on automated testing that will identify these issues in the future.