Base experienced a 33-minute outage on August 5 due to a mismanaged sequencer that was not properly configured to process transactions. The issue began at 6:07 AM UTC when the active sequencer fell behind in block production, leading Conductor, which manages sequencer reliability, to switch to a backup sequencer that was still being set up. As a result, no blocks could be produced until the problem was addressed. The network was fully operational again by 6:40 AM UTC. The incident highlights Base's reliance on Conductor, which creates a potential single point of failure. Following this, Base intends to update its infrastructure to ensure that all sequencers can handle block production if selected. Although this was not the first outage for Base, with a prior 43-minute interruption occurring shortly after its launch, some industry observers viewed the incident as a positive sign of activity in a network with active users. Base's engineering head emphasized the importance of uptime for such services.

Source 🔗