CHYP.ai · ORBIT // Cloudy_Day Security Suite

Crypto exchanges

Degraded / minor incident Kraken status

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

FROM ALL SOURCES

Kraken's status page shows “Degraded / minor incident” in Stablr Euro (EURR) - Ethereum and Stablr USD (USDR) - Ethereum; the vendor is identified the cause. 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: Stablr Euro (EURR) - Ethereum, Stablr USD (USDR) - Ethereum, Osmosis (OSMO)

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started180 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 change5 h 3 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: identified the cause on “Stablr USD (USDR) and Stablr Euro (EURR) Funding Methods Halted”. 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 Kraken'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 “identified the cause”. 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 Kraken. 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 Kraken, 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 Kraken. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Stablr USD (USDR) and Stablr Euro (EURR) Funding Methods Halted

minor identified · started

3 updates

  1. identified

    We have temporarily paused deposits and withdrawals for USDR and EURR due to an issue affecting the underlying smart contract. At this time, there is no indication that Kraken's wallets or systems have been directly compromised. All other funding methods and services continue to operate normally. Our team is actively investigating and working with urgency to resolve the matter. We’ll continue to share updates as more information becomes available.

  2. identified

    We have moved EURR and USDR markets to Post Only due to an issue affecting the underlying smart contract. At this time, there is no indication that Kraken's wallets or systems have been directly compromised. All other funding methods and services continue to operate normally. Our team is actively investigating and working with urgency to resolve the matter. We’ll continue to share updates as more information becomes available.

  3. identified

    We are continuing to work on a fix for this issue.

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