FatTail Outage History

FatTail is up right now

There were 2 FatTail outages since February 3, 2026 totaling 52h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fattail.com

Minor April 13, 2026

AdBook+ System Performance - adbook02.fattail.com only

Detected by Pingoru
Apr 13, 2026, 02:13 PM UTC
Resolved
Apr 14, 2026, 11:03 AM UTC
Duration
20h 50m
Affected: AdBook+ System PerformanceAdBook+ Order Management
Timeline · 4 updates
  1. investigating Apr 13, 2026, 02:13 PM UTC

    We are aware of and urgently investigating an issue with AdBook system performance affecting users of adbook02.fattail.com. 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.

  2. monitoring Apr 13, 2026, 02:36 PM UTC

    Our engineering teams have performed system maintenance which has resolved the performance issue for clients using adbook02.fattail.com. Users should no longer experience issues logging in to, or navigating AdBook. Please contact us at support.fattail.com with questions.

  3. resolved Apr 14, 2026, 11:03 AM UTC

    This issue was fully resolved yesterday and adbook02 health has remained steady since. A postmortem of this incident will be posted once available. Please contact us at support.fattail.com with questions.

  4. postmortem Apr 23, 2026, 05:52 PM UTC

    ### **Summary of Impact** On the morning of April 13, 2026, users of [adbook02.fattail.com](http://adbook02.fattail.com) experienced slow performance and difficulty accessing the system. This included issues logging in, running reports, and navigating between pages. Performance degradation was first observed and reported at approx. 5.30am EST. The FatTail engineering team was able to resolve and restore services at approximately 10.25am EST. ### **Root Cause** The slowdown was caused by degradation of one of the reporting services under a period of elevated request volume. The service continued accepting requests but was unable to process them efficiently which impacted overall system performance. Once the affected service was restarted, the backlog cleared and performance returned to normal. **Mitigation and Next Steps** To prevent recurrence, the FatTail team is implementing the following improvements: 1. Improve system protection and traffic management Adjust service throttling and implement additional safeguards to better control concurrent requests and prevent overload during traffic spikes. 1. Strengthen monitoring, alerting, and traffic analysis Enhance monitoring and alerting to detect and address sources of unusually high traffic. Additionally FatTail Support will provide more frequent ticket communication to affected clients while incidents are active.

Read the full incident report →

Minor February 3, 2026

AdBook+ System Performance

Detected by Pingoru
Feb 03, 2026, 03:49 PM UTC
Resolved
Feb 04, 2026, 11:56 PM UTC
Duration
1d 8h
Affected: AdBook+ Order ManagementAdBook+ Salesforce Integration
Timeline · 5 updates
  1. investigating Feb 03, 2026, 03:49 PM UTC

    We are aware of an issue impacting access to AdBook from Salesforce and are urgently investigating. Some users may encounter a “refused to connect” error or experience issues saving or syncing data. Further updates will be provided here as soon as they are available. Please contact us at support.fattail.com with questions.

  2. identified Feb 03, 2026, 05:51 PM UTC

    We have identified an issue with the Salesforce integration that is affecting access to AdBook for clients who use SSO to authenticate via an MFA provider or Salesforce Identity Provider (IdP). We are actively working with Salesforce to identify the root cause and implement a fix. In the meantime, some users may continue to encounter a “refused to connect” error or experience issues with saving or syncing data. Further updates will be shared as soon as they become available.

  3. identified Feb 03, 2026, 08:37 PM UTC

    The access issue between Salesforce and AdBook was caused by changes introduced by Salesforce in a recent release. Salesforce is actively working to roll back those changes. Following completion, our team will perform validation testing and confirm resolution. Further updates will be provided here as soon as they are available.

  4. monitoring Feb 04, 2026, 03:46 AM UTC

    Salesforce has confirmed that the release change responsible for the issue has been fully rolled back. Since the rollback, our team has confirmed that the AdBook–Salesforce connection is performing as expected. We will continue to monitor closely to ensure ongoing stability. Please contact us at support.fattail.com with questions.

  5. resolved Feb 04, 2026, 11:56 PM UTC

    After monitoring performance throughout the day, we have confirmed that the fix Salesforce released to address the access issue between AdBook and Salesforce has fully resolved the problem. Please contact us at support.fattail.com with questions.

Read the full incident report →

Looking to track FatTail downtime and outages?

Pingoru polls FatTail's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when FatTail reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track FatTail alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring FatTail for free

5 free monitors · No credit card required