On Jan 31, Base experienced elevated transaction drops and inclusion delays. A configuration change to transaction propagation caused the block builder to repeatedly fetch transactions that couldn't be executed due to rapidly rising base fees. We mitigated the issue by rolling back the change and have validated that network stability has been restored. We’re taking steps to prevent this from recurring and improving our response in the event it does happen. This includes optimizing the transaction pipeline by removing unnecessary P2P overhead, and tuning our mempool queues - we expect this work to take approximately one month. Additionally, we're improving our alerting and change monitoring during rollouts of infrastructure changes. Be sure to subscribe to the status page to stay informed of future incidents: