Login
Access to full transaction data on all transactions & addresses
Broadcast and verify transactions with real-time monitoring
Retrieve blockchain data, balances, and transactions
Detailed blockchain history and transaction data for any address.
Full smart contracts metadata, including token symbols & token names
Dedicated nodes infrastructure for leading blockchains using JSON-RPC
Address validation, encoding & cryptographic tasks optimizations
Shared node infrastructure for top blockchains using JSON-RPC.
Real-time notifications for events on top blockchains. Response under 100ms.
Precise blockchain transaction fee estimates based on transaction priority
Sync and manage HD wallets, keys and addresses
Prepare EVM transactions, including token transfers
Access to full transaction data on all transactions & addresses
Get access to unified market data using REST APIs from top crypto exchanges.
Test EVM transactions, optimize gas fees and identify security flaws
Sep 2, 2025 • 4 min
Starknet has been gaining momentum as one of the leading Ethereum Layer-2 scaling solutions. Leveraging zero-knowledge rollups (zk-rollups), Starknet enables developers to build decentralized applications (dApps) with lower transaction costs and higher throughput while maintaining Ethereum’s security level. Designed with scalability, privacy, and developer flexibility in mind, Starknet has become a popular choice for blockchain developers, product teams, and businesses building on top of Ethereum.
However, as with any rapidly evolving technology, challenges emerge. Most recently, Starknet experienced a significant network outage following the release of its much-anticipated Grinta upgrade (v0.14.0), which left users unable to process transactions for hours. This incident raised concerns not only about Starknet’s reliability but also about the potential ripple effects across the ecosystem.
The Grinta upgrade was one of Starknet’s most ambitious technical updates to date. It introduced several key innovations:
These updates promised more robust infrastructure and improved user experience. But when the upgrade went live on September 2, 2025, things did not go as planned.
The Starknet team initially anticipated a short 15-minute downtime to finalize the Grinta deployment. Instead, the network went dark for nearly three to four hours. The root cause was traced to the sequencer, which failed to properly interpret transactions containing Cairo0 code after the upgrade.
This sequencer malfunction had cascading effects:
To restore functionality, Starknet engineers performed a chain reorganization (reorg) from block 1,960,612. This rollback invalidated all transactions submitted between 2:23 AM and 4:36 AM UTC. As a result, developers and end-users had to resubmit their transactions manually after block production resumed.
From a technical perspective, this highlights the fragility of a single point of failure in sequencer-based Layer-2 solutions. While decentralization of sequencers is on Starknet’s roadmap, the Grinta rollout exposed how critical proper testing and compatibility checks are when introducing system-level changes.
For developers and businesses running on Starknet, the outage meant:
For end-users, the most visible impact was the inability to use applications or move assets during the outage window. Importantly, the issue was not tied to infrastructure providers like Crypto APIs, but rather to the underlying Starknet blockchain itself.
This was not Starknet’s first disruption in recent months. In July 2025, Starknet suffered another outage lasting roughly 13 minutes, also linked to sequencer instability. Although shorter, that incident raised early questions about reliability and the risks of centralization in sequencer-based rollups. The Grinta outage, being longer and involving a chain rollback, has amplified those concerns within the blockchain community.
At Crypto APIs, we support Starknet blockchain nodes as part of our Node as a Service (NaaS) offering. This includes both dedicated nodes and shared nodes, giving developers flexibility when connecting their applications to Starknet.
It is important to highlight, however, that while Crypto APIs ensures non-stop availability and reliable infrastructure, outages like the recent Starknet incident are beyond our control. When the blockchain itself halts or rolls back transactions, this impacts all participants equally—whether they are running their own node or connecting via a service provider.
This distinction is crucial for developers and businesses:
By using Crypto APIs Node as a Service, developers benefit from reliability, scalability, and simplified infrastructure management, but should also remain aware of the limitations inherent to the underlying blockchain.
Starknet remains a powerful Layer-2 solution with strong potential, but the Grinta outage serves as a reminder of the technical challenges facing zk-rollup ecosystems. While outages are not uncommon in early-stage blockchains, they underline the importance of decentralization, rigorous testing, and robust communication with users.
For teams building on Starknet, leveraging Crypto APIs Node as a Service ensures uninterrupted node access, whether through dedicated or shared nodes. Still, understanding the difference between infrastructure reliability and blockchain protocol reliability is critical for setting expectations with end-users.
As Starknet continues to evolve and strengthen its sequencing model, developers can expect more resilient infrastructure in the future. Until then, awareness of potential risks is essential. At Crypto APIs, our commitment remains clear: we provide enterprise-grade blockchain infrastructure that is reliable, scalable, and ready to support your applications—even when the blockchains themselves face unexpected challenges.
Copy link