CHYP.ai · ORBIT // Cloudy_Day Security Suite

Fintech apps

Operational Mercury status

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

FROM ALL SOURCES

No sign of a widespread Mercury 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 started18 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 “Duplicated incoming ACH transactions”. 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 Mercury'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 Mercury. 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 Mercury, 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 Mercury may depend on.

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

INCIDENT REPLAY

Duplicated incoming ACH transactions

minor resolved · started · resolved

4 updates

  1. investigating

    We're investigating reports of duplicated incoming ACH transactions that may be impacting some customers. We are aware of this issue and our team is actively looking into it. We'll share an update as soon as we have more information. No action is needed from you at this time.

  2. identified

    We've identified the cause of the duplicate transaction display issue affecting some incoming ACH payments. Our team is currently removing the duplicated incoming ACH entries. We will update this page as we make progress. We'll confirm once the fix has been fully deployed.

  3. monitoring

    The issue affecting the duplicate display of incoming ACH appears to be resolved. Our team is closely monitoring recovery to confirm full stability before closing this incident. We'll post a final update once we've confirmed everything is back to normal.

  4. resolved

    This incident has been resolved. Affected incoming ACH transactions are fully restored and operating normally. What happened: A processing error on our end caused duplicate ACH transactions to appear in some Mercury accounts. During this time, the balance may have temporarily appeared higher or lower than it should have, and may have received duplicate transaction notifications. No further action is needed. 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