We’ve all heard jokes about Solana taking nap breaks… But this time, it was Base. @base went down for 33 minutes on Tuesday after a system glitch froze block production. It started when the main sequencer lagged, and the Conductor (Base’s rerouting tool) tried to switch over, but accidentally picked a test sequencer that wasn’t meant for real action. Boom! the network stalled. The good news? The Base team jumped in fast and got it back up. No chain reorg, no major drama. But yeah, it raised some concerns. Right now, Base only runs one sequencer at a time, chosen by the Conductor. If that one goes down, the whole network can too. Not great when you’ve got over $4.1B in TVL riding on it. They’re already working on upgrades soon, all sequencers will be live and ready to take over instantly. No more single points of failure. Fun fact: this was Base’s second outage. The first was back in September and lasted 43 minutes. Still, the community wasn’t too harsh. Some devs even called it “bullish downtime” the kind of complaints you only hear when a chain has real users. What's your take on this story?
Base Build
Base Build6.8. klo 01.27
Last night, Base Chain experienced a 33 minute network disruption that halted block production. This was due to an automatic handoff to an unhealthy mainnet sequencer in the high-availability cluster. We quickly switched to a healthy mainnet sequencer and Base Chain resumed normal operation. We have run a full postmortem to share what happened, how we addressed the issue, and the steps we are taking to prevent similar incidents in the future.
8,61K