TapClicks Outage History

TapClicks partial outage · 1 active incident View live status →

TapClicks had 32 outages in the last 2 years totaling 412h 5m of downtime — averaging 1.3 incidents per month.

There were 32 TapClicks outages since June 12, 2024 totaling 412h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tapclicks.com

Notice October 11, 2024

Post-Incident Report: TapAccess Smart Connectors - Data Fetching Issue Fixed

Detected by Pingoru
Oct 11, 2024, 05:37 PM UTC
Resolved
Oct 11, 2024, 05:37 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 11, 2024, 05:37 PM UTC

    Summary: We recently resolved an issue that affected customers using TapAccess delivery types for Smart Connectors the morning of Oct 11th. Historical data was not impacted, but the issue prevented new data from being pulled beginning last night. Resolution: Our Engineering Team has applied a fix, and the system is now functioning correctly. New data is being pulled without any problems. Impact: Only customers using TapAccess delivery types were affected. No historical data was lost. Next Steps: We are currently evaluating additional safeguards to prevent similar issues in the future. If you encounter any further issues, please contact us at [email protected]. Thank you

Read the full incident report →

Notice August 30, 2024

Basis BCI Early Access - Fetch Anomaly

Detected by Pingoru
Aug 30, 2024, 03:26 PM UTC
Resolved
Aug 30, 2024, 08:00 PM UTC
Duration
4h 33m
Affected: TapAnalytics/TapReports
Timeline · 3 updates
  1. identified Aug 30, 2024, 03:26 PM UTC

    Issue Summary: We are currently experiencing issues with accessing the Basis BCI Early Access. This issue is impacting customers connected to Connector when attempting to pull new data. However, please note that historical data currently stored on TapClicks remains unaffected. Current Status: We are actively communicating with Basis BCI Team to resolve this issue. We are closely monitoring the situation and will provide updates as soon as more information becomes available. Estimated Time to Resolution (ETA): The resolution timeline is currently dependent on details from our Partners at Basis. Basis BCI is working to address the problem, and we will update you as soon as we have a clearer ETA. We apologize for any inconvenience this may cause and appreciate your patience as we work through this issue.

  2. monitoring Aug 30, 2024, 05:18 PM UTC

    Update Summary: Basis has informed us that they have made a fix on their end. Recommendation: If you are still experiencing issues pulling new data, please re-authenticate your connection to the Basis BCI data source using the new credentials provided by the vendor. We will continue to monitor the connector but if you are still experiencing this issue, please reach out to [email protected]

  3. resolved Aug 30, 2024, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 16, 2024

Google Ads API Error Affecting VIDEO Data View

Detected by Pingoru
Aug 16, 2024, 04:02 PM UTC
Resolved
Aug 19, 2024, 03:20 PM UTC
Duration
2d 23h
Affected: TapAnalytics/TapReports
Timeline · 2 updates
  1. identified Aug 16, 2024, 04:02 PM UTC

    Issue: We are currently experiencing an issue due to an error with the Google Ads API. This error specifically affects the retrieval of data for the VIDEO data view. Impact: The error impacts all accounts connected to Google Ads API. While this issue is preventing the retrieval of new data for the VIDEO data view, please be assured that all previously stored historical data within TapClicks remains intact and unaffected. ETA: Resolution time is dependent on the provider (Google). We are closely monitoring the situation and will provide updates as more information becomes available. Next Steps: We are actively tracking this issue and have engaged with Google Ads API support. We apologize for any inconvenience this may cause and appreciate your patience as we work towards a resolution.

  2. resolved Aug 19, 2024, 03:20 PM UTC

    Google has made updates on their end over the weekend and API calls have been completed for TapClicks Customers connected to Google Ads.

Read the full incident report →

Notice July 19, 2024

Schedule Reports channel filtering

Detected by Pingoru
Jul 19, 2024, 04:45 PM UTC
Resolved
Jul 20, 2024, 05:55 PM UTC
Duration
1d 1h
Affected: TapAnalytics/TapReports
Timeline · 3 updates
  1. identified Jul 19, 2024, 04:45 PM UTC

    Issue: We have identified a temporary issue affecting channel filters, which may have caused discrepancies in the scheduled reports sent out today. Impact: This issue impacts customers who use scheduled reports that include custom channels. ETA: Our engineers are actively working to resolve this issue. If you observe any discrepancies in your scheduled reports, please contact us at [email protected] and we will assist you in resending the reports with accurate information.

  2. monitoring Jul 19, 2024, 05:41 PM UTC

    We have deployed a fix regarding the filter issue and future scheduled reports will filter as intended. If you would like us to help resend reports that went out today with updated data, please reach out to us by emailing [email protected] Thank you

  3. resolved Jul 20, 2024, 05:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 12, 2024

Smart Connector - delay processing email attachments

Detected by Pingoru
Jun 12, 2024, 06:12 PM UTC
Resolved
Jun 16, 2024, 03:00 PM UTC
Duration
3d 20h
Affected: TapAnalytics/TapReports
Timeline · 3 updates
  1. identified Jun 12, 2024, 06:12 PM UTC

    We have identified an issue with delays processing attachments delivered via email to Smart Connectors. Our team is investigating and working on clearing that delay. We apologize for the inconvenience.

  2. monitoring Jun 13, 2024, 01:14 AM UTC

    All delayed email attachments sent to smart connectors should now have been processed, and our team is actively monitoring.

  3. resolved Jun 16, 2024, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →