QuickNode incident

Base Mainnet - Degraded Performance

Resolved after 5 hours 11 minutes, affecting Base - Mainnet and Mainnet — WebSocket API and 1 more, on March 19, 2026.

resolved Mar 19, 2026, 04:53 PM UTC

This incident has been resolved. A problematic block triggered degradation across affected nodes. The root cause has been identified and addressed, and all nodes are now fully synced and operating normally.

Started
Mar 19, 2026, 11:41 AM UTC
Resolved
Mar 19, 2026, 04:53 PM UTC
Duration
5h 11m
Detected by Pingoru
Mar 19, 2026, 11:41 AM UTC

Affected components

Base - MainnetMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams

Update timeline

  1. investigating Mar 19, 2026, 11:41 AM UTC

    We are currently investigating reports of degraded performance affecting Base endpoints. Users may experience elevated latencies and 503 errors when interacting with Base. We are actively investigating the root cause and are in contact with the Base Foundation. We will provide further updates as the situation develops.

  2. monitoring Mar 19, 2026, 12:52 PM UTC

    The root cause has been identified and a fix has been applied. Affected nodes are currently syncing and catching up. We are continuing to monitor the situation closely and will update this page once full stability is confirmed. We apologize for the inconvenience and thank you for your patience.

  3. resolved Mar 19, 2026, 04:53 PM UTC

    This incident has been resolved. A problematic block triggered degradation across affected nodes. The root cause has been identified and addressed, and all nodes are now fully synced and operating normally.

Your product runs on more than QuickNode

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →