Bakkt logo

Is Bakkt Down?

SaaSLive status, outages, and incident history

No. Bakkt is up right now.

Every monitored Bakkt system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Bakkt breaks

Bakkt is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Bakkt status page
How we know: the official Bakkt status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Bakkt Status Summary

As of 12:28 UTC on 9 November 2026, Bakkt is operational. PulsAPI checked Bakkt's official status page and found 15 of 15 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Bakkt, counting degraded performance as up. The latest incident, "Delays in Crypto Transfers", was on Nov 4, 2026 and lasted 79h 59m.

Cite as: PulsAPI, “Bakkt status”, checked 9 November 2026, 12:28 UTC. https://www.pulsapi.com/services/bakkt

Bakkt Component Status

The main Bakkt systems on this page. All 15 are operational right now.

15operational
Bakkt Crypto Trading » Account Opening
Operational
Bakkt Crypto Trading » Batch Allocations
Operational
Bakkt Crypto Trading » Coin Deposits
Operational

12 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Bakkt Crypto Trading » Coin Withdrawals, Bakkt Crypto Trading » EOD Files, Bakkt Crypto Trading » Gift Allocations, Bakkt Crypto Trading » Market Data, Bakkt Crypto Trading » Order Entry - API, Bakkt Crypto Trading » Order Entry - FIX, Bakkt Fiat » Bank Account Linking, Bakkt Fiat » FIAT ACH, Bakkt Fiat » FIAT Wires, Bakkt Link » Account, Bakkt Link » Bakkt Link, Bakkt Link » Crypto.

See all of them free

Component statuses may change independently during partial outages.

Recent Bakkt Outages & Incidents

Incident history from the official Bakkt status page, including resolution updates.

Delays in Crypto TransfersResolved Nov 4, 2026 · 79h 59mResolved

This issue has been resolved. Transfers are processing normally. --- [2026-11-04T11:32:55.818-05:00] (investigating) Hi All - We are currently experiencing delays in processing coin transfers. Transfers may take longer than usual to complete. All pending transactions are queued and will be processed automatically once stability is restored.

Monitoring Industry Security EventsStarted Oct 30, 2026Investigating

We are aware of the security incident affecting a large crypto exchange and the volatility across digital asset markets. We have seen no impact to Bakkt systems, customer assets, or services. Out of an abundance of caution, our security and operations teams are taking additional precautions. These include added monitoring, extra review of certain transactions and partner activity, and close coordination with our liquidity, custody, and banking partners. Some transactions may take longer than usual to process while we complete these checks. Please bear with us if you notice any delay. Your security is our priority, and we will update this page right away if anything changes.

Intermittent Market DataResolved Sep 22, 2026 · 0 minResolved

Between 08:11 and 10:35 UTC on 22 September 2026, a degradation in market data affected our trading platform. During this period, some customers experienced intermittent order rejections. Affected orders were rejected at the point of submission and were not queued for later execution. Customers who received a rejection during this window should resubmit any orders they still wish to place. Customer balances, holdings and settled transactions were not affected. Market data returned to normal and order processing was fully restored as of 11:00 UTC. We are continuing to review the underlying cause and will take steps to prevent a recurrence. If you believe you were materially affected, please contact our support team.

Bakkt Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Bakkt incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 1 day with incidentsNov 9

Going further back: Bakkt uptime by month and every recorded Bakkt outage.

Live Bakkt Outage Reports

Problems reported by engineers using Bakkt. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Bakkt problems reported yet.

Something wrong with Bakkt on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Bakkt

Bakkt publishes a public status page at status.bakkt.com covering 18 components, including Bakkt Link, Account Opening and Bakkt Fiat. PulsAPI tracks Bakkt outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Bakkt uptime at 100.00%. Response times, incident history, and SLA tracking for Bakkt are available on the PulsAPI dashboard.

Bakkt Status FAQ

Is Bakkt down right now?

The verdict at the top of this page comes from the latest poll of the official Bakkt status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Bakkt is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Bakkt recovers.

How do I check Bakkt uptime history?

PulsAPI tracks Bakkt uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Bakkt changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Bakkt outages?

PulsAPI reads the official Bakkt status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Bakkt components?

Yes. PulsAPI monitors 15 individual Bakkt components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Bakkt goes down?

Yes. Create a free account and subscribe to Bakkt: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Bakkt to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Bakkt problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Bakkt?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Bakkt plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Bakkt with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services