Brandfolder Monthly Reports Delayed

Update timeline

1. identified Feb 27, 2026, 09:55 PM UTC

   We have proactively paused the release of our February reports to ensure the highest level of data accuracy. Our team is currently resolving a synchronization issue, and we expect the corrected reports to be available shortly. We apologize for the inconvenience and appreciate your patience while we ensure your data is 100% correct.

2. identified Mar 03, 2026, 03:55 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Mar 09, 2026, 04:38 PM UTC

   We are continuing to work on restoring full service.

4. identified Mar 12, 2026, 09:08 PM UTC

   A fix is being implemented. An update will be shared once completed.

5. identified Mar 16, 2026, 07:05 PM UTC

   We are finalizing the fix for this issue and will have an update shortly.

6. monitoring Mar 24, 2026, 03:02 PM UTC

   We have implemented the fix fully and we are monitoring for stability.

7. resolved Mar 24, 2026, 05:57 PM UTC

   This incident has been resolved.

8. postmortem Mar 25, 2026, 03:05 AM UTC

   On February 25, 2026, a data synchronization issue was identified in Brandfolder's reporting infrastructure. The logical replication pipeline between the production database and the analytics data layer fell out of sync, which caused stale or missing data in Insights dashboards, subscription page metrics, and the Insights Data Connector. Standard monthly reports were proactively paused on February 27 to prevent delivery of inaccurate data, and a partial outage was posted to the status page. Engineering began rebuilding the replication pipeline, but encountered multiple failures during the data catch-up process due to the volume of data \(~5TB\) and recurring initialization errors. The replication pipeline was stabilized on March 16 and data began flowing to the analytics layer. The team then identified and resolved gaps in session data for specific dates, re-ran the affected data pipeline jobs, and verified data parity between the production database and analytics systems. Standard reporting was resumed on March 24, 2026, and the incident was resolved the same day. All previously missed reports have been generated and delivered. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for the replication pipeline, adding automated data health checks, and documenting recovery runbooks to reduce future resolution time.