Live / Quicknode / Incident
Quicknode: Base Mainnet – Delayed transaction inclusion (upstream)
Quicknode · quicknode.comMinor incidentResolved2026-11-02 18:17 UTC
Public — what happened
Summary
Quicknode reported a minor incident on Base Mainnet in which transactions were taking longer than normal to be included in a block, starting at 14:13 UTC on 2026-11-02. The company said the delay came from a problem on the Base sequencer side, and that transactions sent through its endpoints were still being accepted and forwarded normally. At 15:44 UTC Quicknode said Base had put a fix in place and was watching the results, with inclusion times expected to return to normal. The incident was marked resolved at 15:55 UTC.
Affected
Base - Mainnet
Timeline
- Started — 2026-11-02 14:13 UTC
- Investigating — 2026-11-02 14:13 UTC
- Monitoring — 2026-11-02 15:44 UTC
- Resolved — 2026-11-02 15:55 UTC · 1h 42m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Quicknode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Quicknode: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Quicknode report →
More from Quicknode
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.