FatTail experienced a minor incident on January 26, 2026 affecting AdBook+ System Performance and AdBook+ Order Management and 1 more component, lasting 7d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 26, 2026, 04:05 PM UTC
We are aware of and urgently investigating an issue with AdBook system performance. Users may experience latency when accessing or navigating within the system. Further updates will be provided here as soon as they are available. Please contact us at support.fattail.com with questions.
- identified Jan 26, 2026, 05:05 PM UTC
We have identified the issue affecting system performance and are planning to release a fix shortly. Thank you for your patience as we work to restore performance.
- monitoring Jan 26, 2026, 06:37 PM UTC
Following a maintenance update at approximately 9:30a PST AdBook+ system performance has returned to normal levels. We continue to closely monitor system health and will leave this incident open. Please contact us at support.fattail.com with questions.
- resolved Feb 02, 2026, 06:54 PM UTC
This incident has been resolved.
- postmortem Feb 05, 2026, 08:01 PM UTC
### **Summary of Impact** On Monday, January 26, some users experienced slow performance and intermittent issues when loading or saving campaigns and line items in the platform. The issue began around 10:45 AM ET. A fix was deployed by 11:30 AM ET, which restored normal performance. Later in the afternoon, a portion of users experienced a recurrence of intermittent slowness. A second improvement was deployed that evening, and by 9:00 PM ET all performance issues were fully resolved. ### **Root Cause** The performance degradation was caused by changes introduced in the v4.04.01 release deployed on Friday January 23rd, which led to higher-than-expected system resource usage under certain conditions. This created slower response times for users when executing certain actions in AdBook. **Mitigation** Our engineering team: * Optimized the affected processing logic to restore normal system performance * Corrected an issue that was generating excessive system activity * Verified platform stability following deployment ### **Next Steps** To reduce the likelihood of similar issues in the future, we are: * Expanding performance and load testing to better cover complex order and campaign scenarios * Enhancing test coverage for recent release changes prior to deployment We apologize for the disruption and appreciate your patience. Please contact Support if you have any additional questions.