FatTail Outage History

FatTail is up right now

FatTail had 6 outages in the last 2 years totaling 2328h 4m of downtime — averaging 0.2 incidents per month.

There were 6 FatTail outages since April 27, 2025 totaling 2328h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fattail.com

Notice September 29, 2025

AdBook+ System Performance | Affecting adbook03.fattail.com

Detected by Pingoru
Sep 29, 2025, 03:32 PM UTC
Resolved
Oct 01, 2025, 01:22 PM UTC
Duration
1d 21h
Affected: AdBook+ System PerformanceAdBook+ Salesforce Integration
Timeline · 5 updates
  1. investigating Sep 29, 2025, 03:32 PM UTC

    We are aware of and urgently investigating an issue affecting clients who login via adbook03.fattail.com. Users may encounter errors saving lines, running reports or navigating areas of the system, including sync operations with Salesforce. 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. FatTail Support

  2. investigating Sep 29, 2025, 03:57 PM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 29, 2025, 04:30 PM UTC

    Performance on adbook03.fattail.com is currently stable. We are continuing to research root cause and are actively monitoring all systems. Further updates will be provided as they become available. Thank you FatTail Support

  4. monitoring Sep 29, 2025, 07:41 PM UTC

    Performance on adbook03.fattail.com remains stable. We are continuing to actively monitor all systems.

  5. resolved Oct 01, 2025, 01:22 PM UTC

    This incident is being closed. A postmortem will be published as a follow up. Please contact us at support.fattail.com with questions. FatTail Support

Read the full incident report →

Notice July 28, 2025

AdBookOMS single-sign on access issue

Detected by Pingoru
Jul 28, 2025, 03:31 AM UTC
Resolved
Jul 28, 2025, 07:42 AM UTC
Duration
4h 10m
Affected: AdBook+ Order ManagementAdBook+ Salesforce Integration
Timeline · 3 updates
  1. investigating Jul 28, 2025, 03:31 AM UTC

    We are aware of and investigating an issue affecting users accessing AdBookOMS via single-sign on integrations. This includes access via the Salesforce 'Access AdBook' integration. Users are receiving a 502 bad gateway error when attempting to access the system. Users who log directly in to AdBook are not impacted by this incident. FatTail engineering are investigating with urgency. Updates will be provided as soon as they are available. Thank you for your patience while we work to resolve this issue. FatTail Support

  2. identified Jul 28, 2025, 07:23 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jul 28, 2025, 07:42 AM UTC

    Users are now able to successfully log in to AdBook via SSO integrations. We will follow up with details on cause of issue once a full report is available. Thank you for your patience while we worked to resolve this issue. FatTail Support.

Read the full incident report →

Minor April 27, 2025

Issue with 'EditIO' and 'EditDrop' Links in AdBook+ OMS Email Notifications

Detected by Pingoru
Apr 27, 2025, 05:37 PM UTC
Resolved
Jul 14, 2025, 02:36 PM UTC
Duration
77d 20h
Affected: AdBook+ Order Management
Timeline · 2 updates
  1. identified Apr 27, 2025, 05:37 PM UTC

    We have identified an issue impacting the 'EditIO' and 'EditDrop' links in OMS email notifications. When users click these links, they are redirected to their AdBook+ landing page instead of the intended Campaign or Drop. This issue does not impact the Portal workflow — email links continue to redirect correctly to specific campaigns within the Portal UI. Our team is actively working on a fix and will provide an update as soon as we have a timeline for the release. We appreciate your patience as we resolve this issue. If you have any questions or concerns, please contact us at support.fattail.com.

  2. resolved Jul 14, 2025, 02:36 PM UTC

    This issues was resolved in our 3.98.01 release.

Read the full incident report →