CHYP.ai · ORBIT // Cloudy_Day Security Suite

Productivity & files

Operational Zapier status

zapier.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Zapier problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started81 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Freshservice - Webhook delivery disruption”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside Zapier's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

We don't map other services that depend on Zapier. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Zapier, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Zapier may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Zapier. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Freshservice - Webhook delivery disruption

none resolved · started · resolved

5 updates

  1. investigating

    Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.

  2. investigating

    We are still investigating the disruption with Freshservice and have touched base with their team to continue digging into this. We will continue to share further information as it becomes available. We appreciate your patience while our team works on this.

  3. investigating

    We’re still investigating the disruption with Freshdesk. If you are experiencing issues related to this, please reach out here: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

  4. investigating

    The Freshservice disruption is still under investigation. The Freshservice team has confirmed the issue and is working to implement a fix. We’ll provide the next update once we know more. If you’re experiencing this issue, please reach out to our Support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

  5. resolved

    Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes. If you experience ongoing issues, contact Support by clicking above or go to: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thank you for your patience.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next