Base Mainnet | Safe Head Delay

This incident has been resolved.

Batching performance has recovered and safe head is advancing normally. We’re continuing to monitor to ensure the delta stays within expected bounds.

We've identified the cause of the safe head latency as an issue with batching performance. Batches are now posting, and we're working to close the gap between the safe and unsafe heads.

Safe head is currently trailing the unsafe head on Base Mainnet. We're working to optimize batching performance to restore normal progression.

For time-sensitive operations, we recommend:
* Use higher fees for time-sensitive transactions
* Ensure retry logic is in place

We’ll continue to post updates as we progress toward a resolution.