TapClicks Outage History

TapClicks is up right now

There were 4 TapClicks outages since February 2, 2026 totaling 46h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tapclicks.com

Notice April 2, 2026

Degraded Performance: X (Twitter) API Connectivity Issues

Detected by Pingoru
Apr 02, 2026, 03:32 PM UTC
Resolved
Apr 02, 2026, 05:15 PM UTC
Duration
1h 42m
Affected: TapAnalytics/TapReports
Timeline · 2 updates
  1. monitoring Apr 02, 2026, 03:32 PM UTC

    We are currently investigating reports of data fetch failures and connectivity issues affecting the X (Twitter) data source. This appears to be related to a wider service disruption with the X API, which is impacting third-party platforms globally. What this means for you: Data Refreshes: Scheduled data fetches for X (Twitter) may fail or be delayed. Dashboards: Some widgets and reports relying on X data may show "No Data" or encounter loading errors. Connection Management: Attempts to re-authenticate or add new X connections may be unsuccessful at this time. Next Steps: Our engineering team is monitoring the situation closely. We will provide further updates as more information becomes available or as service is restored by X. Once the API is stable, TapClicks will automatically attempt to backfill any missed data. No action is required from you at this time. We apologize for any inconvenience caused by this external disruption.

  2. resolved Apr 02, 2026, 05:15 PM UTC

    X (Twitter) has confirmed that the technical issues affecting their API and platform services have been resolved. Our system is currently processing a backfill to retrieve any data that was missed during the outage. You should see your dashboards fully updated within the next few hours, depending on the volume of data. Note on Connections: If you attempted to re-authenticate or add an X connection during the outage and encountered an error, you may now retry those actions. All existing connections should resume functioning automatically. Thank you for your patience while we monitored this external service disruption.

Read the full incident report →

Notice March 5, 2026

Delayed Data Loads for The Trade Desk

Detected by Pingoru
Mar 05, 2026, 11:56 PM UTC
Resolved
Mar 06, 2026, 09:31 PM UTC
Duration
21h 34m
Affected: TapAnalytics/TapReports
Timeline · 3 updates
  1. monitoring Mar 05, 2026, 11:56 PM UTC

    We are currently investigating a service disruption with The Trade Desk (TTD) connector. Multiple client instances are experiencing delays in daily data fetches. While fetches typically complete within an hour, current reports are remaining in a PENDING state for extended periods. What We Know So Far: Root Cause: Vendor-side dependency issue within The Trade Desk's reporting API. Impact: Reports for some clients are stuck in "Pending" status on the TTD side, preventing TapClicks from successfully ingesting the latest data. Data Freshness: As of today, most impacted dashboards will show the latest available data from March 2, 2026. Data for March 3 and March 4 remains delayed. Our Action Plan: We are in direct contact with The Trade Desk, and they have confirmed they are aware of the outage. We will continue to monitor on our end will provide updates accordingly.

  2. monitoring Mar 06, 2026, 07:25 PM UTC

    We are seeing significant improvement in data ingestion for The Trade Desk (TTD). As of today, the majority of data fetches are completing successfully. While some fetches remain in progress, we have verified that the mappings for these active fetches are already showing successful results We will continue to monitor on our end as we await for confirmation by The Trade Desk Team.

  3. resolved Mar 06, 2026, 09:31 PM UTC

    The Trade Desk (TTD) team has confirmed that a fix has been implemented on their end to resolve the reporting outage. We are now seeing data fetches for customers completing successfully, including the backfill of data for March 3 and March 4.While most fetches have already finished, we are still monitoring a few remaining active sessions. We have verified that even for the fetches still in progress, data mappings are successful, indicating that the data is flowing correctly. If you are still encountering discrepancies, please contact [email protected]

Read the full incident report →

Notice February 13, 2026

Status Update: CallRail Connectivity Issues

Detected by Pingoru
Feb 13, 2026, 07:45 PM UTC
Resolved
Feb 13, 2026, 10:21 PM UTC
Duration
2h 35m
Affected: TapAnalytics/TapReports
Timeline · 2 updates
  1. identified Feb 13, 2026, 07:45 PM UTC

    Summary We are currently investigating a widespread issue affecting the CallRail connector. While data fetches may appear to complete, the data is not being pulled properly into the system. This is causing existing mapping lists to display as "no longer available" across all connected instances. Issue: Our team has observed a change in how account identifiers are being returned through the CallRail API. Impact: This change affects the system's ability to match your existing configurations with the data currently being provided. Scope: This is currently impacting all instances connected to CallRail. Historical data already loaded into TapClicks remains fine but you may observe discrepancies or prevented from retrieving newer data until this issue is resolved. Next Steps: TapClicks is dependent on CallRail for updates and is coordinating with the CallRail technical team to reestablish our connection to the CallRail API. Next Update: We will provide further information once the technical alignment between both platforms is finalized.

  2. resolved Feb 13, 2026, 10:21 PM UTC

    We have successfully addressed the synchronization issue with the CallRail connector. Following a technical shift in how account identifiers were being returned from the vendor, we have updated our mapping logic to align with these changes. Key Technical Updates Identifier Shift: CallRail transitioned from alphanumeric company IDs (e.g., COM37eb...) to a 9-digit numeric format (e.g., 735338535). Fetch Performance: We have confirmed that data fetches are now completing successfully and populating correctly into the system. Mapping Restoration: Previously "no longer available" mapping lists are being updated to reflect these new IDs. If you haven't already done so, you may need to refresh your mapping list for the update. Current Progress Our engineering team has verified that the data flow is stable but will be monitoring in the next coming days. If you are still experiencing issues with CallRail, please reach out to [email protected]

Read the full incident report →

Notice February 2, 2026

Potential Google API Data Delays

Detected by Pingoru
Feb 02, 2026, 07:52 PM UTC
Resolved
Feb 03, 2026, 04:48 PM UTC
Duration
20h 56m
Affected: TapAnalytics/TapReports
Timeline · 2 updates
  1. monitoring Feb 02, 2026, 07:52 PM UTC

    Monitoring Google API Data Delays Incident Status: Investigating Affected Services: Google Ad Manager / Google Connectors We are currently investigating an issue where data pulled from Google platforms via API may be delayed or incomplete. This is due to an ongoing service incident on Google’s side impacting reporting and API responses. What customers may see: Delays in Google data appearing in TapClicks Failed or stalled data pulls for Google data services Potentially Incomplete or missing metrics for recent reporting periods Current status: We've primarily seen this affecting Google Ads Manager and Google Analytics so far. Some other Google services api pulls may also be impacted. TapClicks systems are operating normally. The issue originates from Google’s reporting infrastructure: https://ads.google.com/status/publisher/incidents/RauRLSuJsK5ZwApqdzEu Our team is actively monitoring Google’s progress and will resume normal syncs once the service stabilizes No action is required at this time. Data will backfill automatically once Google resolves the issue. We will provide updates as more information becomes available.

  2. resolved Feb 03, 2026, 04:48 PM UTC

    Google has made an updated fix at 10PM UTC. We are now updating our status page accordingly as the fetches have been completing. If you are still observing issues with Google connectors, please reach out to [email protected].

Read the full incident report →

Looking to track TapClicks downtime and outages?

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

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

5 free monitors · No credit card required