TapClicks Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded TapClicks Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Worldwide PHP Security Event: How TapClicks Is Protecting YouTapClicks is fully back online. Thank you for your patience while we proactively took the platform offline during the worldwide PHP security event. What happened: On October 20, the PHP security team gave advance… | 4h 21m | Resolved |
| Oct 21, 2026 | Industry-Wide PHP Security Vulnerability: TapClicks Proactive MaintenanceOngoing communication about this issue will be covered under the incident "Worldwide PHP Security Event: How TapClicks Is Protecting You" | 8h 27m | Resolved |
| Oct 19, 2026 | Resolving Partial Data Load FailuresThis issue has been resolved - if you have any questions about your scheduled reports, please reach out to support@tapclicks.com. | 172h 41m | Resolved |
| Sep 30, 2026 | The Trade Desk: Delayed Data for September 26–27This incident has been resolved. | 453h 49m | Resolved |
| Apr 2, 2026 | Degraded Performance: X (Twitter) API Connectivity IssuesX (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… | 1h 42m | Resolved |
| Mar 5, 2026 | Delayed Data Loads for The Trade DeskThe 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… | 21h 34m | Resolved |
| Feb 13, 2026 | Status Update: CallRail Connectivity IssuesWe 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… | 2h 35m | Resolved |
| Feb 2, 2026 | Potential Google API Data DelaysGoogle 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… | 20h 56m | Resolved |
| Nov 14, 2025 | Reddit Ads Connection IssueCurrent 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… | 283h 50m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next TapClicks incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This TapClicks Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TapClicks acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single TapClicks outage in this window ran 18d 21h, against a mean recovery of 4d 11h. If you depend on TapClicks in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.