Live / Kraken / Incident
Kraken: FIX API connectivity issues
Kraken · kraken.comMinor incidentResolved2026-10-29 00:53 UTC
Public — what happened
Summary
Kraken said that starting at 22:54 UTC on October 28, 2026, some clients could not reconnect to its FIX API after maintenance finished earlier that day, and some saw their connection attempts rejected. The company said its other trading interfaces were not affected. At 00:26 UTC on October 29 Kraken reported that it had put a fix in place and was watching the results, and the incident was marked resolved at 00:53 UTC. The company did not state a cause in the text provided.
Affected
FIX
Timeline
- Started — 2026-10-28 22:54 UTC
- Investigating — 2026-10-28 22:54 UTC
- Monitoring — 2026-10-29 00:26 UTC
- Resolved — 2026-10-29 00:53 UTC · 1h 59m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Kraken against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Kraken: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Kraken report →
More from Kraken
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.