CHYP.ai · ORBIT // Cloudy_Day Security Suite

Databases & data

Degraded / minor incident Fivetran status

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

FROM ALL SOURCES

Fivetran's status page shows “Degraded / minor incident” in Facebook Pages and Stripe; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.

confidence: low Vendor: minor issue · users: normal · routing: no data.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Facebook Pages, Stripe, Stripe test mode

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started13 h 15 min
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 change1 h 12 min

Evidence

  • Official page: Degraded / minor incident (“Minor Service Outage”). evidence confidence: high
  • Vendor stage: resolved on “3rd Party: Facebook Pages connections are failing with the error: “An error has occurred. No further information is available.””. 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 Fivetran'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: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

We don't map other services that depend on Fivetran. 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

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

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

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

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

INCIDENT REPLAY

3rd Party: Facebook Pages connections are failing with the error: “An error has occurred. No further information is available.”

minor resolved · started · resolved

4 updates

  1. identified

    The issue has been identified and we are working to resolve it.

  2. identified

    We identified that Meta has started returning a new error code (0) in API responses. Our connector does not currently handle this response, causing affected connections to fail. Our team is investigating the issue and working on a fix. Next Expected Update: 1 hour

  3. monitoring

    Meta has stopped returning the new error code (0), and affected connections have resumed syncing. Next update: 1 hour

  4. resolved

    This incident has been resolved. Failure rates have returned to normal, and affected connectors are syncing successfully. <b>Incident Summary:</b> Description: Facebook Pages connections began failing after Meta started returning a new error code (0) in its API responses. The connector did not handle this response. Timeline: The incident began on November 20, 2026, at 16:30 UTC and was resolved on November 20, 2026, at 19:40 UTC. Cause: Meta began returning error code 0 in API responses. Resolution: The failures stopped after Meta stopped returning this error. We also implemented a workaround to improve how the connector handles this response and reduce the likelihood of similar failures in the future.

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