Is Fireblocks down?

Last checked 1m ago
Current status
Fireblocks is up

No incidents right now.

Get alerts when Fireblocks breaks →

Free · no credit card

Official status page: https://status.fireblocks.com · Polled every 5 minutes · 121 components tracked

Real-time Fireblocks status, recent outages, and incident history — pulled directly from Fireblocks's official status page at https://status.fireblocks.com every 5 minutes. Pingoru tracks 121 Fireblocks services and has captured 30 incidents in the last 90 days (99.68% uptime). Get email, Slack, Discord, or webhook alerts the moment Fireblocks reports a new incident — free for 5 monitors, no credit card.

Users who monitor Fireblocks also follow these Cryptocurrency services: Coinbase Gemini Kraken Blockchain Solana Helium QuickNode Coins.ph CEX.IO CoinMarketCap View all 6,000+ providers
Fireblocks uptime 99.68% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. FB514U: Litecoin transaction delays during Litecoin chain reorganisation
    Resolved —
    Started Apr 25, 2026, 03:57 PM UTC · Resolved Apr 25, 2026, 03:57 PM UTC
    Litecoin
    4 updates · show timeline
    • investigating · Apr 25, 2026, 02:03 PM UTC

      Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status of Litecoin blockchain. We are actively investigating this issue.

    • identified · Apr 25, 2026, 02:19 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 25, 2026, 03:19 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 25, 2026, 03:57 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. FB513U: Transaction processing delays with Litecoin transactions
    Resolved 49m
    Started Apr 25, 2026, 12:24 PM UTC · Resolved Apr 25, 2026, 01:13 PM UTC
    Litecoin
    4 updates · show timeline
    • investigating · Apr 25, 2026, 12:24 PM UTC

      Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status of Litecoin blockchain. We are actively investigating this issue

    • identified · Apr 25, 2026, 12:31 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 25, 2026, 01:06 PM UTC

      A fix has been implemented, and we are monitoring the results. In addition, we have identified an issue with the Litecoin chain itself where new blocks are being created with massive delay.

    • resolved · Apr 25, 2026, 01:13 PM UTC

      The Incident has been resolved. We are actively monitoring the Litecoin chain itself for any other stability issues.

    Latest: The Incident has been resolved. We are actively monitoring the Litecoin chain itself for any other stability issues.

  3. FB512U: Intermittent delays with outgoing transactions
    Resolved 26m
    Started Apr 23, 2026, 03:49 AM UTC · Resolved Apr 23, 2026, 04:16 AM UTC
    Transactions engine
    4 updates · show timeline
    • investigating · Apr 23, 2026, 03:49 AM UTC

      Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.

    • identified · Apr 23, 2026, 04:13 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 23, 2026, 04:15 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 23, 2026, 04:51 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Fireblocks outage history

25 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 7 incidents
  • FB514U: Litecoin transaction delays during Litecoin chain reorganisation Resolved
    Started Apr 25, 2026, 03:57 PM UTC · Resolved Apr 25, 2026, 03:57 PM UTC · —
  • FB513U: Transaction processing delays with Litecoin transactions Resolved
    Started Apr 25, 2026, 12:24 PM UTC · Resolved Apr 25, 2026, 01:13 PM UTC · 49m
  • FB512U: Intermittent delays with outgoing transactions Resolved
    Started Apr 23, 2026, 03:49 AM UTC · Resolved Apr 23, 2026, 04:16 AM UTC · 26m
  • FB511U: Authentication Issues with Fireblocks Console and API calls failures Resolved
    Started Apr 20, 2026, 05:23 PM UTC · Resolved Apr 20, 2026, 05:37 PM UTC · 13m
  • FB510U: Transaction Engine Delay Resolved
    Started Apr 20, 2026, 08:26 AM UTC · Resolved Apr 20, 2026, 08:47 AM UTC · 20m
  • FB509U: Intermittent Issues with API timeout {Error codes 500} Resolved
    Started Apr 06, 2026, 01:54 PM UTC · Resolved Apr 06, 2026, 02:01 PM UTC · 6m
  • FB508U: Delays with outgoing transactions Resolved
    Started Apr 01, 2026, 07:44 AM UTC · Resolved Apr 01, 2026, 07:56 AM UTC · 11m

See Fireblocks in your Pingoru dashboard

Monitor Fireblocks alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Fireblocks to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Fireblocks incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Fireblocks or see every provider at once.

Maintenance calendar

Scheduled Fireblocks maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Fireblocks status change, one inbox

Pingoru watches Fireblocks's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Fireblocks reports on 121 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Fireblocks alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Fireblocks maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Fireblocks services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Fireblocks from the same account, with per-user notification preferences for any monitor.

Get notified on Fireblocks status changes

Pingoru watches Fireblocks's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Fireblocks free

Monitor Fireblocks along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Fireblocks and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Fireblocks uptime & incident history

See 90 days of Fireblocks uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Fireblocks uptime history

Frequently asked questions

What is Fireblocks's uptime?
Over the last 90 days, Fireblocks reported 99.68% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.fireblocks.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Fireblocks's uptime history rolling forward in real time.
Has Fireblocks had outages in 2026?
Yes — Fireblocks has had 30 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Fireblocks outage?
The most recent Fireblocks incident was "Blockchain Canton Halt During an Upgrade on April 26th, 2026", which started on April 26, 2026 and was resolved on April 26, 2026. Pingoru captured this directly from https://status.fireblocks.com. See the full incident card above for affected components and the update timeline.
How often does Fireblocks have outages?
Based on the last 90 days, Fireblocks averages 10.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Fireblocks's status page?
Fireblocks's official status page is https://status.fireblocks.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Fireblocks down right now?
Fireblocks is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Fireblocks reports a change. Current status is based on 121 tracked services.
How does Pingoru know if Fireblocks is down?
We read https://status.fireblocks.com directly, using Fireblocks's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Fireblocks has an outage?
Create a free Pingoru account and add Fireblocks as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Fireblocks's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Fireblocks incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Fireblocks issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Fireblocks status?
We use Fireblocks's own status page at https://status.fireblocks.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Fireblocks components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Fireblocks's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Fireblocks free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →