← Back to the carnage
ZAPIER

🟠 Zapier's Zap History decided to play hide-and-seek with your automation records. Engineering found the problem and is slowly coaxing the runs back out of whatever digital witness protection program they joined. They're trickling in like a bathroom faucet that needs a plumber. (Auto-resolved: no updates in 24h)

⏰ Sep 09, 2026 Fixed (for now) spotted via status_rss

// The official story

Zap History not displaying Zap runs

// Status page says

Status: Identified We've identified the root cause for Zap runs not displaying in the Zap History, and our Engineering team is working on a resolution. Zap runs are slowly appearing again in the Zap history, and we'll confirm once all Zap runs can be accessed. For any questions, please reach out to our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

🔗 Official status page (for the PR-approved version)

https://status.zapier.com//incidents/01M23MR3RRFCQ119H6VX8N9D3M

Zapier's Greatest Hits

🟢 ZAPIER 4d ago
🟡 Zapier's S3 bucket got flagged by Google Safe Browsing, so now your file downloads come with a free 'this might infect your computer' warning. Nothing says 'enterprise-grade' like your own infrastructure ratting you out to security algorithms. (Auto-resolved: no updates in 24h)
🟢 ZAPIER Oct 05, 2026
🟡 Zapier's Facebook and Microsoft login buttons led to the void after authentication. Engineers found the culprit and shipped a fix, now playing the waiting game to see if it actually stuck or just created new and exciting problems. (Auto-resolved: no updates in 24h)
🟢 ZAPIER Sep 08, 2026
⚪ Zapier's webhook triggers decided to take an unscheduled siesta between 8:15–9:50 AM ET, leaving Zap workflows wondering if they'd been ghosted. Action steps also threw a tantrum. Infrastructure gremlins have been exorcised and flows are back to normal, though some missed events are being replayed like a bad recording. (Auto-resolved: no updates in 24h)
🟢 ZAPIER Sep 04, 2026
🟡 Zapier's Freshservice connector decided webhooks are more of a suggestion than a promise. Team's investigating like they lost the keys to production. Your automations are having an existential crisis while support waits by the phone. (Auto-resolved: no updates in 24h)