Tapclicks 中断历史

1. 2026年10月21日 UTC 05:35identified

   10月20日,PHP安全团队发布PHP中两个关键弱点的预告(CVE-2026-109618和CVE-2026-109619),以严重程度评为9.2分之10(远程代码执行). 上游维护者安排了今天,10月21日 UTC下午14:00/10:00AM EDT的紧急安全发布. 鉴于这些弱点的严重性,以及围绕官方补丁发布前泄露的开采细节的公众讨论,我们有意决定将TapClicks平台暂时下线,直到供应商的修复能够被应用. 这种主动孤立的做法符合主要网络安全咨询的指导,包括CERT-EU咨询2026-018。 受影响的是什么: 核心 TapClicks 应用程序目前无法使用 。 一旦恢复平台服务,数据处理队列和日常数据负载将自动相继恢复处理. 下一步: PHP安全团队发布后,我们将尽快部署安全补丁,完成环境完整性检查,并恢复全面服务. 我们将在早上7点半前,或者在得到新的信息后,在东部发布下一次更新。 我们为您工作日的中断而道歉,并赞赏您在我们优先考虑平台安全时的理解。 如需紧急询问,请与我们的支助小组联系,地址是:[email protected].

2. 2026年10月21日 UTC 08:33identified

   我们的团队正全天候工作,准备发布官方的PHP安全补丁并监测任何事态发展. 我们将提供更多的最新消息.

3. 2026年10月21日 UTC 12:01identified

   我们的工程队仍然处于积极待命状态,准备正式的上游PHP安全发布,定于今天上午10:00(协调世界时14:00)举行。 发布后,我们预计一个部署、核查和测试窗口大约两小时后,核心应用服务才能恢复上网。 为确保环境稳定,随着服务检查的完成,将逐步恢复平台访问和数据处理队列. 我们赞赏您的耐心,并将在上午10时30分左右,在获得新信息后,提供我们的最新状况.

4. 2026年10月21日 UTC 13:15identified

   我们正在继续改善基础设施,以缓解全球安全的脆弱性.

5. 2026年10月21日 UTC 14:03resolved

   Ongoing communication about this issue will be covered under the incident "Worldwide PHP Security Event: How TapClicks Is Protecting You"

自动翻译自官方事件更新。

1. 2026年10月19日 UTC 14:22identified

   由于基础设施配置的改变,今天上午我们大约25%的数据负荷进程失败了。 我们已经解决了这个问题,目前正在重新运行失败的数据载荷。 我们还正在评估对预定报告的影响,并将在数据装入完成后立即重新分发任何受影响的报告。 我们为不便而道歉,并感谢你的耐心.

2. 2026年10月19日 UTC 17:54identified

   数据负载失败已经重新启动,我们正在监测。 一旦报告完成,我们将能够重新开始分发已排定的受影响报告.

3. 2026年10月20日 UTC 03:51identified

   目前,所有数据负荷完成的事例都受到预定报告的影响。 我们将在上午提供另一个最新情况。 谢谢你的耐心.

4. 2026年10月20日 UTC 15:27monitoring

   绝大多数受影响的预定报告都备受不满。 我们仍然在监测,并将在今天晚些时候提供最新情况.

5. 2026年10月26日 UTC 19:04resolved

   这个问题已经解决 -- -- 如果您对预定提交的报告有任何问题,请联系@tapclicks.com.

自动翻译自官方事件更新。

1. 2026年9月30日 UTC 16:33investigating

   我们看到贸易股在9月26日和27日的报告提供方面出现延误,因此这些日期的数据可能不完整。 受影响的用户可能还会看到较长的刷新时间或偶尔无法获取此数据源。 我们的小组正在与贸易股合作,并正在改进我们的一体化处理延迟报告的方式。 所缺失的数据一旦可用,将自动被回填,所以不需要任何动作. 随着问题的进展,我们将在此发布最新情况.

2. 2026年10月19日 UTC 14:23resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年4月2日 UTC 15:32monitoring

   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. 2026年4月2日 UTC 17:15resolved

   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.

1. 2026年3月5日 UTC 23:56monitoring

   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. 2026年3月6日 UTC 19:25monitoring

   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. 2026年3月6日 UTC 21:31resolved

   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]

1. 2026年2月13日 UTC 19:45identified

   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. 2026年2月13日 UTC 22:21resolved

   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]

1. 2026年2月2日 UTC 19:52monitoring

   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. 2026年2月3日 UTC 16:48resolved

   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].

1. 2025年11月14日 UTC 23:57identified

   Current Status: We are currently experiencing an issue with the Reddit Ads connector. Some users may be encountering connection or reauthentication problems when attempting to use the service. What’s Happening: Users might face difficulties connecting to the Reddit Ads platform or may be prompted to reauthenticate multiple times. What We're Doing: We are in active communication with Reddit’s support team to resolve the issue as quickly as possible. Our team is working diligently with Reddit to address the problem, and we will provide further updates as soon as we have more information. Impact: Connection issues may occur intermittently and potential disruption in pulling recent Reddit data Next Steps: We are closely monitoring the situation and will provide updates on progress. Thank you for your patience!

2. 2025年11月20日 UTC 22:36identified

   Thank you for your continued patience. We understand the frustration this delay is causing, as it is impacting many of our customers that leverages the Reddit Ads connector. Unfortunately, we are still awaiting support from Reddit to resolve the issue, and TapClicks is dependent on their assistance to move forward. We will provide further updates as soon as we have more information. If you haven't already done so, we encourage you to reach out to your Reddit Representative to help escalate the matter.

3. 2025年11月26日 UTC 19:47resolved

   Current Status: The issue with the Reddit Ads connector has been resolved. What Happened: There were connection and reauthentication issues that affected some users attempting to access the API. The issue has now been fixed with the help of Reddit, and the service is functioning normally again. Action Required: If you have not already reauthenticated, you may need to do so in order to reconnect to Reddit Ads to reestablish the feed. Thank you for your patience and support

1. 2025年10月20日 UTC 13:56investigating

   The major AWS outage this morning is impacting all our clients on our Big Data Package. We are currently investigating to see if other clients are impacted and will post updates as they become available. Media reference: https://www.cnn.com/business/live-news/amazon-tech-outage-10-20-25-intl

2. 2025年10月20日 UTC 14:27investigating

   As an update, our team has identified that the following data sources were also impacted. Some of them are already showing signs of improvement and we will monitor throughout the day: - Amazon Ads - Marchex - Reddit Ads - Twilio - Viant DSP (Adelphic) - Smart Connector Email Delivery Note that other data sources/vendors that rely on AWS infrastructure, such as the Amazon delivery types in Smart Connectors, may also be impacted.

3. 2025年10月21日 UTC 14:32monitoring

   The global AWS outage that was impacting our vendors has been resolved, and all services are operational. We will continue to monitor performance closely. If you experience any further issues, please contact our support team at [email protected].

4. 2025年10月23日 UTC 15:55resolved

   No new issues related to the AWS outage on Monday have been identified as part of our monitoring in the last 2 days, so we are now closing this incident. If you experience any further issues or have any questions, please contact our support team at [email protected].

1. 2025年9月25日 UTC 19:52investigating

   We are currently observing sporadic failures when connecting to Google Services APIs. Other API users are reporting similar issues, and this appears to be a problem on Google’s side. Impact This may affect TapClicks customers who are pulling data from Google services through our integrations. Customers may experience intermittent disruptions when retrieving or syncing data. Actions Taken We have reported the issue to Google Support. We are monitoring the situation closely and will update as more information becomes available. Next Update We will provide updates as soon as Google shares additional information or the situation stabilizes.

2. 2025年9月26日 UTC 16:19monitoring

   Update Fetches are successfully completing today, and we are seeing improvements in the API's performance. While we're still waiting for a confirmation from Google, the fetches are now completing as expected, and there are no ongoing disruptions. We are continuing to monitor API fetches closely to ensure everything runs smoothly. We will keep you informed of any significant changes or updates. Thank you for your patience as we work through this. Please feel free to reach out if you encounter any issues.

3. 2025年9月30日 UTC 16:06resolved

   This incident has been resolved.

1. 2025年8月26日 UTC 19:56identified

   We have identified an issue affecting some Smart Connectors with sub-level data views. The issue is causing: - Slower than usual data loads - Inaccurate results in some cases, due to duplicate or additional rows being created Smart Connectors with a single-level data view (no additional views configured) are not impacted. Our engineering team has identified the root cause and is currently deploying a fix. After the fix is in place, we will also: - Clean up the problematic rows - Re-load the affected data to ensure accuracy We will continue to provide updates as remediation progresses. If you have questions or need assistance, please reach out to [email protected]

2. 2025年8月27日 UTC 01:20identified

   The team is finalizing the logic to clean up problematic rows tonight. Once complete, we will be triggering data reloads that will run for part of the day on Wednesday. We will provide other updates as they become available. Thanks for your patience as we resolve this.

3. 2025年8月27日 UTC 13:53identified

   Problematic rows have been removed overnight and data reloads are now in progress.

4. 2025年8月27日 UTC 22:05identified

   Data reloads have completed for most Smart Connectors that have 2 levels (parent level + 1 sublevel deep). Our team is still working on addressing issues with Smart Connectors that are more than 2 levels deep (meaning, they have sublevels of sublevels, or deeper) and we will provide more updates as they become available. Rest assured that resolving this is our top priority and the team is working around the clock to fix the remaining impacted Smart Connectors.

5. 2025年8月28日 UTC 15:28identified

   Problematic rows have been removed from impacted Smart Connector sublevels (levels 3 and below) for all customers except one, with whom we are in direct communication. Data reloads are still running on some instances, but have completed on most. We will provide more updates as they become available.

6. 2025年8月29日 UTC 20:20identified

   The data correction process is now complete for all customers. Our team is proactively running data integrity checks against backups over the coming days to ensure all data was accurately restored. While we expect a full recovery, if you notice any discrepancies within your multi-level Smart Connectors, please contact our support team at [email protected]. We are ready to investigate further or initiate a historical data reload if needed.

7. 2025年9月4日 UTC 13:59resolved

   The recent issue affecting data in Smart Connector sublevel views is now resolved. We have completed verifying data integrity and restored all affected historical records. Service is now operating normally. Should you see any further issues, please contact our support team at [email protected] for immediate assistance. Our team is completing a full root cause analysis to improve system stability and has already implemented several preventative measures. Thank you for your patience.

1. 2025年8月6日 UTC 00:29identified

   Issue: We are encountering errors during the processing of DOMAIN reports from Simpli.fi due to invalid values in the ‘Time Event Date’ field for multiple clients. While previously stored data is unaffected, this issue may hinder the processing of new data. Impact: Users utilizing DOMAIN reports are impacted preventing the processing of new data of the domain reports, though previously stored data remains unaffected. ETA: This is a vendor-dependent issue. We have reported the problem to Simpli.fi and are awaiting their resolution. Further updates will follow as soon as we receive more information.

2. 2025年8月6日 UTC 17:42resolved

   Simpli.fi has pushed a fix on their end on the Time Event Date field. We have observed daily fetches have completed successfully. If you are still experiencing issues, please let us know at [email protected]

1. 2025年7月8日 UTC 19:28identified

   We have identified an issue impacting clients on our Big Data Package where some data and widgets are returning errors. Our team is investigating.

2. 2025年7月8日 UTC 20:37resolved

   The issue has now been resolved and widgets are loading properly on instances on our Big Data Package. We apologize for the inconvenience.

1. 2025年6月5日 UTC 14:04investigating

   A subset of our customers connected to Simpli.fi are experiencing data delays due to a technical issue on our end. Impacted customers can see this by looking at "Connections with issues to be investigated by TapClicks" on the main tab of their Data Load Status dashboard and have received notifications via email already if they have configured these on the Notifications tab of the Data Load Status dashboard. Our team is actively working on resolving the issue and we will provide updates as they become available. We apologize for the inconvenience.

2. 2025年6月13日 UTC 15:31resolved

   This incident has been resolved.

1. 2025年6月3日 UTC 15:16identified

   Impact: Data Delays for Simpli.fi-Connected Customers Monitoring We are currently observing intermittent connection issues between TapClicks and Simpli.fi, as reported by our partner at Simpli.fi. This is impacting customers whose data sources are connected to Simpli.fi via TapClicks. What you may experience: Delays in the availability of new data from Simpli.fi Historical data previously collected remains accessible and unaffected Simpli.fi has identified the issue and is actively working toward a resolution on their end. TapClicks will continue to monitor the situation closely and provide updates as we receive them. We appreciate your patience and understanding. The TapClicks Team

2. 2025年6月4日 UTC 14:54resolved

   Update: All of Simpli.fi reporting services were restored starting around 7PM (CT) last evening and fetches for today have been completing without errors. If you are still experiencing issues with your Simpli.fi connection, please reach out to [email protected] Thank you

1. 2025年5月23日 UTC 16:00identified

   Description: Tapclicks is currently experiencing an outage with the X (formerly Twitter) Ads Connector. This issue is due to an external service disruption on X Ads' side, which is impacting our ability to retrieve new advertising data via their API. Impact: New data from X Ads is currently unavailable in Tapclicks. Previously imported data remains intact and accessible. Next Steps: We are monitoring the situation and awaiting further updates from X. We will provide additional information as it becomes available. Thank you for your patience and understanding.

2. 2025年5月27日 UTC 16:53resolved

   X Ads have restored their API over the weekend and after monitoring, we can confirm a majority of customers fetches have been successfully completing. We will close this incident as the connection now appears to be stable. If you are still facing issues with the X Ads connection, please reach out to support. Thank you, The TapClicks Team

1. 2025年4月23日 UTC 19:39identified

   We are currently investigating an issue affecting the retrieval of recent metrics from the Instagram API. A recent change made by Instagram appears to be causing interruptions for some users attempting to access this data. Our team is actively working to adapt to the update. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

2. 2025年4月24日 UTC 01:27monitoring

   Instagram has deprecated the "Impressions" field from the Professional API that was causing recent fetch issues. TapClicks has updated our system to discontinue requests for the impression metric to unblock data fetches for customers. Your historical impressions data that was previously stored within TapClicks will still be accessible in TapClicks but new impression data will no longer be supported by the Instagram API. We will be working on introducing new fields per Instagram's recent changes.

3. 2025年4月24日 UTC 18:24monitoring

   Fetches today continue to complete after close monitoring. We are marking the incident for fetch failures as resolved in the meantime. We are still in the process of working with the new metric fields as an enhancement separately.

4. 2025年5月23日 UTC 15:58resolved

   This incident has been resolved.

1. 2025年4月16日 UTC 15:38identified

   Issue Summary We are currently experiencing an issue with data ingestion from The Trade Desk connector. Specifically, some Conversions and Data Elements API reports have been disabled on The Trade Desk system side. The Trade Desk team is actively investigating the root cause. Impact This impacts users who are connected to The Trade Desk Connectors leveraging these specific reports. Please check the Data Load Status page to see whether your instance is affected. This impacts the ability to fetching new TTD data while previously stored data in TapClicks remains unaffected by this issue. Next Steps & ETA This issue is vendor-dependent. We've submitted an urgent request to The Trade Desk, who have acknowledged receipt and investigating on their end. We will share updates as soon as we receive more information from The Trade Desk team.

2. 2025年4月17日 UTC 19:21monitoring

   Update: The Trade Desk Fetches for today has been completing for a majority of our customer post communication with The Trade Desk Team. We are still in discussions with the TTD team and will continuing to monitor fetches. Thank you for your patience.

3. 2025年4月18日 UTC 16:54resolved

   Update: After recent monitoring, we are no longer seeing fetch issues for conversions for our API fetches. If you are still encountering issues, please reach out to [email protected]. Thank you, The TapClicks Team

1. 2025年3月19日 UTC 16:11investigating

   Incident Summary: We are currently investigating an issue affecting some of our customers who are connected to the Google Ads API. Due to recent changes made on Google's end, certain customers are experiencing difficulties with fetching data. Current Status: Our team is actively working with Google and collaborating closely with their team for a resolution. What’s Affected: Customers with active Google Ads API connections may experience intermittent data fetching failures or delays. Affected customers may notice incomplete or outdated data in their dashboards. Next Steps: We will continue to monitor the situation and keep you updated as we work with Google to resolve this issue. We are prioritizing this matter and will provide a follow-up once we have more information or once the issue has been resolved.

2. 2025年3月20日 UTC 17:48resolved

   Google Ads services were successfully restored following a fix implemented on March 19th. After thorough monitoring, we can confirm that the intermittent Fetch issue has been resolved. If you continue to experience any problems with the Google Ads connector, please contact us at [email protected]. Thank you, The TapClicks Team

1. 2025年3月19日 UTC 15:47identified

   We have identified that there is incident going on with one of our provider is impacting clients on the BigData package. We are working closely with the provider to get the service back ASAP. This is a global incident that was reported by the BigData data engine provider. This is impacting TapAnalytics and TapReport among other services. Customers not on BigData packages are not impacted.

2. 2025年3月19日 UTC 19:21monitoring

   Update: Our BigData engine provider has implemented a fix on their end. Customers hosted on BigData servers are being restored, and we are seeing a significant improvement in dashboard performance. We will continue to closely monitor performance in collaboration with the provider to ensure stability moving forward.

3. 2025年3月20日 UTC 15:33resolved

   After carefully monitoring, all customers are stable with the fix done by the BigData provider yesterday. This incident is now resolved. Please reach out to [email protected] if you are still observing any issues. Thank you, The TapClicks Team