- Detected by Pingoru
- May 02, 2026, 10:59 AM UTC
- Resolved
- May 02, 2026, 11:51 AM UTC
- Duration
- 52m
Affected: Solana
Timeline · 4 updates
-
investigating May 02, 2026, 10:59 AM UTC
Symptoms include outgoing Solana transactions stuck on "BROADCASTING/SUBMITTED/QUEUED" status or failing with "Internal Fireblocks Error."
-
identified May 02, 2026, 11:38 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 02, 2026, 11:50 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 02, 2026, 11:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 01:52 AM UTC
- Resolved
- May 01, 2026, 02:22 AM UTC
- Duration
- 29m
Affected: WorldChain
Timeline · 3 updates
-
investigating May 01, 2026, 01:52 AM UTC
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status for Worldchain transactions. We are actively investigating this issue.
-
monitoring May 01, 2026, 02:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 01, 2026, 02:27 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 03:57 PM UTC
- Resolved
- Apr 25, 2026, 03:57 PM UTC
- Duration
- —
Affected: Litecoin
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 12:24 PM UTC
- Resolved
- Apr 25, 2026, 01:13 PM UTC
- Duration
- 49m
Affected: Litecoin
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 03:49 AM UTC
- Resolved
- Apr 23, 2026, 04:16 AM UTC
- Duration
- 26m
Affected: Transactions engine
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 05:23 PM UTC
- Resolved
- Apr 20, 2026, 05:37 PM UTC
- Duration
- 13m
Affected: Web consoleAPI
Timeline · 3 updates
-
identified Apr 20, 2026, 05:23 PM UTC
Our authentication infrastructure is currently experiencing an issue that is causing login failures for Console and initiating API calls. We are currently investigating this issue.
-
monitoring Apr 20, 2026, 05:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 20, 2026, 05:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 08:26 AM UTC
- Resolved
- Apr 20, 2026, 08:47 AM UTC
- Duration
- 20m
Affected: Transactions engine
Timeline · 5 updates
-
investigating Apr 20, 2026, 08:51 AM UTC
Our transaction processing infrastructure is currently experiencing latency with transactions handling. This may cause transactions to fail with INTERNAL_ERROR
-
identified Apr 20, 2026, 08:53 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 20, 2026, 08:54 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 20, 2026, 09:18 AM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 20, 2026, 11:21 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 01:54 PM UTC
- Resolved
- Apr 06, 2026, 02:01 PM UTC
- Duration
- 6m
Affected: API
Timeline · 5 updates
-
investigating Apr 06, 2026, 01:46 PM UTC
Our API infrastructure is currently experiencing an issue which is causing timeout or errors while calling the API endpoints. We are actively investigating this issue.
-
investigating Apr 06, 2026, 01:48 PM UTC
We are continuing to investigate this issue.
-
identified Apr 06, 2026, 01:53 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 06, 2026, 02:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 06, 2026, 02:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 07:44 AM UTC
- Resolved
- Apr 01, 2026, 07:56 AM UTC
- Duration
- 11m
Affected: Transactions engine
Timeline · 4 updates
-
investigating Apr 01, 2026, 07:55 AM UTC
We are currently investigating this issue.
-
identified Apr 01, 2026, 07:57 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 01, 2026, 08:03 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 01, 2026, 08:17 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 28, 2026, 01:28 PM UTC
- Resolved
- Mar 28, 2026, 06:59 PM UTC
- Duration
- 5h 30m
Affected: Binance Smart Chain
Timeline · 3 updates
-
investigating Mar 28, 2026, 01:28 PM UTC
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on BNB_BSC blockchain. We are actively investigating this issue.
-
monitoring Mar 28, 2026, 02:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 28, 2026, 06:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 05:36 PM UTC
- Resolved
- Mar 27, 2026, 05:58 PM UTC
- Duration
- 22m
Affected: Litecoin
Timeline · 3 updates
-
investigating Mar 27, 2026, 05:36 PM 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.
-
monitoring Mar 27, 2026, 05:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 27, 2026, 06:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 01:38 PM UTC
- Resolved
- Mar 26, 2026, 01:50 PM UTC
- Duration
- 11m
Affected: Binance Smart Chain
Timeline · 4 updates
-
investigating Mar 26, 2026, 01:48 PM UTC
We are currently investigating this issue.
-
identified Mar 26, 2026, 01:50 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 26, 2026, 01:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 26, 2026, 02:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 04:15 PM UTC
- Resolved
- Mar 23, 2026, 03:51 PM UTC
- Duration
- —
Affected: Transactions engine
Timeline · 3 updates
-
investigating Mar 23, 2026, 03:41 PM 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.
-
monitoring Mar 23, 2026, 03:50 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 23, 2026, 04:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 02:23 PM UTC
- Resolved
- Mar 20, 2026, 03:00 PM UTC
- Duration
- 37m
Affected: Binance Smart Chain
Timeline · 3 updates
-
identified Mar 20, 2026, 02:23 PM 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.
-
monitoring Mar 20, 2026, 02:48 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 20, 2026, 07:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 07:10 PM UTC
- Resolved
- Mar 17, 2026, 07:25 PM UTC
- Duration
- 14m
Affected: Solana
Timeline · 3 updates
-
identified Mar 17, 2026, 07:10 PM UTC
Our transaction processing infrastructure is currently experiencing an issue that is causing Solana transactions to fail with INTERNAL_ERROR
-
monitoring Mar 17, 2026, 07:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 17, 2026, 07:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 07:39 PM UTC
- Resolved
- Mar 12, 2026, 08:15 PM UTC
- Duration
- 36m
Affected: TON
Timeline · 3 updates
-
identified Mar 12, 2026, 07:39 PM UTC
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on TON blockchain, missing incoming TON transactions, and balance update with delays. We are actively investigating this issue.
-
monitoring Mar 12, 2026, 08:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 08:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 06:17 PM UTC
- Resolved
- Mar 10, 2026, 06:25 PM UTC
- Duration
- 8m
Affected: Fireblocks mobile app
Timeline · 3 updates
-
identified Mar 10, 2026, 06:17 PM UTC
Our Mobile notification processing infrastructure is currently experiencing an issue that is causing delayed notifications on the mobile application. We are actively investigating this issue.
-
monitoring Mar 10, 2026, 06:25 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 10, 2026, 06:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 08:27 AM UTC
- Resolved
- Mar 10, 2026, 08:40 AM UTC
- Duration
- 12m
Affected: Web console
Timeline · 4 updates
-
investigating Mar 10, 2026, 08:27 AM UTC
We're currently experiencing an issue that is causing login issues to the console. We are currently investigating this issue.
-
identified Mar 10, 2026, 08:38 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 10, 2026, 08:38 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 10, 2026, 08:54 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 06:02 AM UTC
- Resolved
- Mar 09, 2026, 06:05 AM UTC
- Duration
- 3m
Affected: Canton
Timeline · 2 updates
-
investigating Mar 09, 2026, 06:02 AM UTC
Our transaction processing infrastructure is currently experiencing an issue with Canton transactions. We are actively investigating this issue.
-
resolved Mar 09, 2026, 06:11 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2026, 10:12 AM UTC
- Resolved
- Mar 07, 2026, 10:00 PM UTC
- Duration
- 11h 47m
Affected: Transactions engine
Timeline · 9 updates
-
investigating Mar 07, 2026, 10:12 AM UTC
Our transaction processing infrastructure is currently experiencing an issue causing with finalizing transactions. Symptoms include outgoing transactions remaining in a proseccing states. We are investigating the issue.
-
investigating Mar 07, 2026, 10:14 AM UTC
We are continuing to investigate this issue.
-
investigating Mar 07, 2026, 10:16 AM UTC
We are continuing to investigate this issue.
-
investigating Mar 07, 2026, 10:30 AM UTC
We are continuing to investigate this issue.
-
investigating Mar 07, 2026, 10:30 AM UTC
We are continuing to investigate this issue.
-
identified Mar 07, 2026, 03:32 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 07, 2026, 04:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 07, 2026, 04:01 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 07, 2026, 04:24 PM UTC
This incident has been resolved. The root cause was a major service disruption from Amazon Route53 https://health.aws.amazon.com/health/status
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 02:51 PM UTC
- Resolved
- Feb 26, 2026, 03:43 PM UTC
- Duration
- 52m
Affected: TON
Timeline · 5 updates
-
investigating Feb 26, 2026, 02:16 PM UTC
We are currently investigating this issue.
-
identified Feb 26, 2026, 02:26 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 26, 2026, 03:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Feb 26, 2026, 03:13 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 26, 2026, 03:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 08:03 PM UTC
- Resolved
- Feb 23, 2026, 09:00 PM UTC
- Duration
- 56m
Affected: API
Timeline · 6 updates
-
investigating Feb 23, 2026, 08:03 PM UTC
Our API infrastructure is currently experiencing an issue which is causing timeout or errors while calling the API endpoints with {"message":"The request has expired","code":-10} We are actively investigating this issue.
-
identified Feb 23, 2026, 08:04 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 23, 2026, 08:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
identified Feb 23, 2026, 08:14 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 23, 2026, 08:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 23, 2026, 09:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 11:05 AM UTC
- Resolved
- Feb 18, 2026, 04:59 PM UTC
- Duration
- 5h 53m
Affected: Transactions engine
Timeline · 5 updates
-
investigating Feb 18, 2026, 11:21 AM UTC
Our transaction processing infrastructure is currently experiencing an issue causing with finalizing transactions. Symptoms include outgoing transactions remaining in a proseccing states. We are investigating the issue.
-
identified Feb 18, 2026, 11:25 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Feb 18, 2026, 11:28 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Feb 18, 2026, 11:35 AM UTC
The fix has been implemented and we're monitoring the results. Impacted transactions might be failed with 'INTERNA_ERROR' status.
-
resolved Feb 18, 2026, 04:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 09:47 PM UTC
- Resolved
- Feb 16, 2026, 10:02 PM UTC
- Duration
- 14m
Affected: Transactions engine
Timeline · 3 updates
-
investigating Feb 16, 2026, 09:47 PM UTC
Our transaction processing infrastructure is currently experiencing an issue causing with finalizing transactions. Symptoms include outgoing transactions remaining in a "Submitted" state. We are investigating the issue.
-
monitoring Feb 16, 2026, 10:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 16, 2026, 10:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 15, 2026, 10:20 AM UTC
- Resolved
- Feb 15, 2026, 11:30 AM UTC
- Duration
- 1h 10m
Affected: Webhooks
Timeline · 5 updates
-
investigating Feb 15, 2026, 12:23 PM UTC
Our Webhook(s) processing infrastructure is currently experiencing an issue causing a delay in sending the Webhook(s). We are actively investigating this issue.
-
investigating Feb 15, 2026, 12:24 PM UTC
We are continuing to investigate this issue.
-
identified Feb 15, 2026, 12:27 PM UTC
The issue was identified and we re-triggered the webhook notifications.
-
monitoring Feb 15, 2026, 12:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 15, 2026, 12:34 PM UTC
This incident has been resolved.
Read the full incident report →
