Is FatTail down?

We are aware of and urgently investigating an issue with AdBook system performance. Users may encounter intermittent errors trafficking lines, checking availability, and running reports. Further updates will be provided here as soon as they are available. Thank you for your patience while we work to restore performance. Please contact us at support.fattail.com with questions.

Our engineering team has identified the issue impacting system performance and completed system optimizations. Performance remains stable at this time. We will leave this incident open for monitoring. Please reach out via support.fattail.com if you have questions or concerns.

This incident has been resolved.

### **Summary of Impact** On the afternoon of June 22, 2026, users of [adbook03.fattail.com](http://adbook02.fattail.com/) and [adbook04.fattail.com](http://adbook04.fattail.com) experienced trafficking errors and slow response time on campaign uploads and reporting. Performance degradation was first observed and reported at approx. 4:30pm EST. The FatTail engineering team was able to resolve and restore services at approximately 6:25pm EST. ### **Root Cause** The degradation was caused by elevated request volume that put high pressure on the service caching mechanisms, which caused a slowdown in response time. **Mitigation** There were two steps taken to mitigate the issue: 1. The reporting services were restarted to clear out orphaned \(timed out\) requests that were queued up in the caching service. 2. Cache parameters were updated to provide more resources to handle elevated request volume.  ### **Next Steps** The team is implementing monitoring to raise alerts when cache resources are out of normal operating zones.

We are currently investigating an issue introduced with the Salesforce Summer '26 Release that is impacting the **AdBook Refresh Process** for some clients. As a result, AdBook refreshes may fail and generate errors. Example Error: An internal server error has occurred An error has occurred while processing your request. The Salesforce: The #1 Agentic AI CRM  support team has been notified of the problem. If you believe you have additional information that may be of help in reproducing or correcting the error, please contact Salesforce Support. Please indicate the URL of the page you were requesting, any error id shown on this page as well as any other related information. We apologize for the inconvenience. Thank you again for your patience and assistance. And thanks for using Salesforce: The #1 Agentic AI CRM ! Error ID: 2126748694-89894 (251024430) If you encounter this error, please complete the following steps: 1. Navigate to Setup → Apex Jobs in Salesforce. 2. Locate any AdBookBatchRefreshOutOfSync jobs that are currently failing. 3. Abort all failing AdBookBatchRefreshOutOfSync jobs. 4. Once the jobs have been aborted, create a Salesforce Support Case. 5. Include the full error message displayed in the Status Detail field of the failed Apex Job when submitting your case. This information will assist Salesforce in identifying and resolving the issue more quickly. We are actively working with Salesforce to understand the root cause and will provide additional updates as more information becomes available. Thank you for your patience and cooperation. Please contact us via support.fattail.com if you have any questions or concerns.

We have identified the cause of the refresh errors as related to the recent Salesforce release. Why Summer '26 Could Have Caused This?  Even without any changes to your org or the AdBook package, the Summer '26 platform release (API v67.0, VF runtime v262) may have introduced one or more of the following changes that caused previously valid UDF values to exceed Salesforce limits:  1. Visualforce Runtime Upgrade (v262): Summer '26 shipped a new VF runtime version that changed how POST request parameters and form data are serialized. This can result in longer string representations being passed to underlying managed package methods — even when the underlying data has not changed.  2. SOAP/WS Array Serialization Changes: The failing method accepts a AdBookWS$ArrayOfDynamicPropertyValue parameter — a SOAP-based array type. Platform changes to how these types are marshalled before being passed to the PL/Java layer can cause the serialized string to grow beyond the declared limit.  3. Stricter PL/Java Enforcement: In some platform hardening releases, oversized PL/Java call argument values that were previously tolerated (or silently truncated) are now rejected with a hard exception. This would explain why the same data worked before Summer '26 but fails now. Recommended Next Steps: An updated Managed Package is available (v3.92) to handle longer parameter values as generated by the Summer '26 VF runtime. IF you have been impacted by this issue, please via support.fattail.com to coordinate the install the new version of the Managed Package in your Salesforce sandbox environment. After completing User Acceptance Testing (UAT) and confirming that everything is functioning as expected, you can proceed with the installation in your production environment.

We have confirmed that this incident can be resolved by upgrading to AdBook Managed Package version 3.92 or later. The updated managed package uses an alternative data point, which prevents the Salesforce internal governor limit from being reached. Additionally, we have verified that the Apex jobs responsible for asynchronous processing will be restored once the impacted jobs are aborted. If you have been impacted by this issue, please work via support.fattail.com to coordinate the install the new version of the Managed Package in your Salesforce sandbox environment. After completing User Acceptance Testing (UAT) and confirming that everything is functioning as expected, you can proceed with the installation in your production environment.