Tokeny incident
Network issue Base mainnet - blockchain service degraded
Resolved after 7 hours 16 minutes, on June 25, 2026.
Base Mainnet Block Production Disruption Component: Base network connectivity Time: ~16:07 – 18:46 UTC, 25 Jun 2026 This was caused by an upstream Base Mainnet incident during the Beryl Upgrade activation, where a consensus problem caused an invalid block to be sequenced and halted block production. This is tracked by our RPC provider here: https://status.quicknode.com/incidents/mpft7mgzwmzp The node has since caught up and is fully in sync with the network. All Base services are operating normally. No action is required from users.
Update timeline
- resolved Jun 26, 2026, 05:12 AM UTC
Base Mainnet Block Production Disruption Component: Base network connectivity Time: ~16:07 – 18:46 UTC, 25 Jun 2026 This was caused by an upstream Base Mainnet incident during the Beryl Upgrade activation, where a consensus problem caused an invalid block to be sequenced and halted block production. This is tracked by our RPC provider here: https://status.quicknode.com/incidents/mpft7mgzwmzp The node has since caught up and is fully in sync with the network. All Base services are operating normally. No action is required from users.
Your product runs on more than Tokeny
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services