Starknet testnet (Sepolia) – slow block creation alert
Timeline · 2 updates
- investigating May 26, 2026, 02:54 AM UTC
Starknet is taking longer than expected to produce a block.
- resolved May 26, 2026, 03:39 AM UTC
This incident has been resolved.
Starknet had 10 outages in the last 2 years totaling 48h 45m of downtime — averaging 0.4 incidents per month.
There were 10 Starknet outages since September 1, 2025 totaling 48h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
Starknet is taking longer than expected to produce a block.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Starknet is taking longer than expected to produce a block.
This incident has been resolved.
Starknet mainnet was down for 11 minutes, due to a planned upgrade - the 0.14.1-committer upgrade
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Starknet didn't produce blocks for 9 min, due to a timeout in one of the services. The team is monitored the continous operation and a bugfix to prevent this incident from repeating again will be released soon.
This incident has been resolved.
Transactions are not being received by the gateways.
This incident has been resolved.
Starknet was down for a few hours, and there was a reorg that dropped the transactions between blocks 1962681 and 1962873. A fix has been implemented and we're now monitoring.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cairo0 code is currently unusable within Starknet mainnet and Sepolia. We identified the bug and working to fix it asap
A fix has been implemented and we are monitoring the results.
This incident has been resolved.