Supermetrics incident

Service disruption: The Trade Desk, May 21, 2026

Minor Resolved View vendor source →

Supermetrics experienced a minor incident on May 21, 2026 affecting The Trade Desk, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
May 21, 2026, 11:18 AM UTC
Resolved
May 22, 2026, 11:33 AM UTC
Duration
1d
Detected by Pingoru
May 21, 2026, 11:18 AM UTC

Affected components

The Trade Desk

Update timeline

  1. investigating May 21, 2026, 11:18 AM UTC

    We're currently investigating reports of an issue affecting The Trade Desk connector. The Trade Desk's API is currently returning permissions-related errors, which prevents data from being retrieved successfully via our connector. Affected users may see error messages such as "Login failed. Missing required partner-level reporting permissions", "Couldn't validate data access eligibility. Please re-authenticate to fix the issue.", or similar permission-related messages. Our team is actively investigating the root cause and working to identify a resolution. We'll share an update as soon as we have more information. Thank you for your patience while we look into this.

  2. monitoring May 21, 2026, 12:29 PM UTC

    Following careful monitoring, we're seeing a return to normal operations on The Trade Desk connector. Permission-related errors should no longer appear, and we'll continue to closely monitor the connector's behaviour over the next 24 hours to ensure stability. If you're still experiencing any issues, please don't hesitate to reach out to our Support team. Thank you for your patience and understanding throughout this incident.

  3. resolved May 22, 2026, 11:33 AM UTC

    Following a 24-hour monitoring period, we're no longer seeing any issues with The Trade Desk connector, and the previously reported errors are no longer occurring. We're considering this incident fully resolved. If you're still experiencing any related issues, please don't hesitate to reach out to our Support team. Thank you for your patience as we worked to resolve this disruption.