Is Base down?

Last checked 4m ago
Current status
Base is up

No incidents right now.

Official status page: https://status.base.org · Polled every 5 minutes · 22 components tracked

Base is operational right now. Last checked 4m ago; the most recent incident resolved 13h ago.

Real-time Base status, recent outages, and incident history — pulled directly from Base's official status page at https://status.base.org every 5 minutes. Pingoru tracks 22 Base services and has captured 12 incidents in the last 90 days (98.58% uptime). Get email, Slack, Discord, or webhook alerts the moment Base reports a new incident — free for 5 monitors, no credit card.

Users who monitor Base also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Base uptime 98.58% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 2m
    Started Jul 28, 2026, 01:10 PM UTC · Resolved Jul 28, 2026, 03:13 PM UTC
    Batch submission
    Timeline · 2 updates
    • identified · Jul 28, 2026, 01:10 PM UTC

      Base Mainnet's Safe head is delayed. New block production is progressing normally; this incident affects only data batching to Ethereum L1.

    • resolved · Jul 28, 2026, 03:13 PM UTC

      Safe head is progressing normally

    Latest: Safe head is progressing normally

  2. Resolved
    Started Jul 21, 2026, 08:54 PM UTC · Resolved Jul 21, 2026, 07:30 PM UTC
    Timeline · 1 update
    • resolved · Jul 21, 2026, 08:54 PM UTC

      Between UTC 19:50 and 20:42, Base Mainnet experienced reduced capacity on the Flashblocks websocket stream. Clients likely experienced delays in receiving messages and rate limits when connecting.

    Latest: Between UTC 19:50 and 20:42, Base Mainnet experienced reduced capacity on the Flashblocks websocket stream. Clients likely experienced delays in receiving messages and rate limits …

  3. Resolved 1d 4h
    Started Jun 25, 2026, 04:03 PM UTC · Resolved Jun 26, 2026, 08:03 PM UTC
    DepositsWithdrawalsBlock productionClient Software
    Timeline · 12 updates
    • investigating · Jun 25, 2026, 04:03 PM UTC

      Base mainnet block production is currently unhealthy. We're investigating the issue now.

    • investigating · Jun 25, 2026, 04:24 PM UTC

      We are continuing to investigate this issue.

    • identified · Jun 25, 2026, 04:52 PM UTC

      We have identified the issue with a problematic block interfering with subsequent block building. The team is working on several threads to remediate and we will continue to post updates as soon as we have them.

    • identified · Jun 25, 2026, 05:21 PM UTC

      We continue to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. Internal sequencer and nodes have preliminarily recovered, the team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.

    • identified · Jun 25, 2026, 05:51 PM UTC

      Sequencing of new blocks has resumed and internal nodes are syncing correctly. We continue to investigate the root cause while monitoring internal nodes for stability. For ecosystem node runners - *Base nodes will need to be restarted to recover syncing*. We will continue to investigate and provide updates as we have them.

    • monitoring · Jun 25, 2026, 05:58 PM UTC

      We have recovered healthy blockbuilding and confirmed that ecosystem-wide infrastructure is able to recover syncing. We continue monitoring to ensure stability. Notably, we expect the Beryl hardfork to activate as planned at 18:00 UTC. We will continue to investigate the root cause and share a full post-mortem once our investigation concludes.

    • monitoring · Jun 25, 2026, 07:22 PM UTC

      Base sequencer and supporting systems remain stable, blocks are being produced normally, and we have verified widespread recovery in the ecosystem. Any remaining Base nodes that are stuck at block 47806542 will recover upon restart and syncing. The team has found the root cause for this halt and is verifying a fix to ensure it cannot recurr. We’ll share a full post mortem including RCA with the ecosystem based on our learnings and fixes as a top priority. We'll continue to monitor all systems to ensure overall network health and stability persists.

    • investigating · Jun 26, 2026, 03:33 PM UTC

      Base mainnet block production is currently unhealthy. We're investigating the issue now.

    • identified · Jun 26, 2026, 03:34 PM UTC

      Base Mainnet is experiencing a chain halt with the similar symptoms. We're actively working on resuming block production.

    • identified · Jun 26, 2026, 03:47 PM UTC

      Block production is resumed. Node operators will need to restart their Base Mainnet nodes in order to resume syncing.

    • monitoring · Jun 26, 2026, 04:11 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Jun 26, 2026, 08:03 PM UTC

      Block production has been succesfully progressing for Base Mainnet. A detailed postmortem will be be published to outline the technical root cause.

    Latest: Block production has been succesfully progressing for Base Mainnet. A detailed postmortem will be be published to outline the technical root cause.

  4. Resolved 9d 19h
    Started Jun 12, 2026, 09:28 PM UTC · Resolved Jun 22, 2026, 04:34 PM UTC
    Client Software
    Timeline · 3 updates
    • investigating · Jun 12, 2026, 09:28 PM UTC

      We're aware that base mainnet has peering issues for newly started nodes and are actively working on a fix to address that. For nodes that are struggling to find peers, we recommend adding below cli args to your reth node and restart for now. ``` --trusted-peers enode://674db972a48b9cab934407c9e28c50fb3c95719272d314dd408ef82804796e06e5de6f991db4e9f33b2b0f09f1ddf3d91f59cd6b3f4b183052efc3d88455d5ac@13.221.49.63:30303?discport=30304,enode://174bcf56adbfbd8eb6fa1e680c356a495d4a4dd638ede1187846f748bf85a9a7396feb64bcd8e725509efdf85362928b71ac50ad59fd73f44aad7103c56e94ac@54.161.193.150:30303?discport=30304,enode://0d5988e13d93d7b96f89767d64445d0b03ca1ad1d7e17a19c60e0997a3bb27217d8f0fca3353abb051bf2b10b10be73d4c2250a15cc1f9e3d8dd5b770fadaf38@54.209.136.129:30303?discport=30304,enode://843e9e53a61bee5bf6f7c2739455ed61ef1056172812123a3f7d6f3f10d12f7c0dc8d7a4bda966ddd4a1d1b61d58bff5558f924b3f0ca84e9e8c0e6feb277142@98.80.147.106:30303?discport=30304,enode://3f4dba3d8b19727f942c0dd63b9d5a2c87aa5cf175bd6a86b78d7913950333382f3befc09f7c0e6af36451091f5d031b2d6db2996480b5c261812ddd76708524@3.81.131.168:30303?discport=30304,enode://3081267a138669585724beec40a422f5f2c8e7f050c5845936420e679c48b43e413106c220b6aa8cd9636042962f2b2ab02e3701f6d8d9233075061cafcfe3b6@34.203.10.78:30303?discport=30304 ```

    • identified · Jun 15, 2026, 05:59 PM UTC

      If you find yourself still unable to find peers, please try to delete /$RETH_DATA_FOLDER/discovery-secret file (by default /data if you're using base/node) and restart the node.

    • resolved · Jun 22, 2026, 04:34 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 19d 18h
    Started Jun 02, 2026, 10:32 PM UTC · Resolved Jun 22, 2026, 04:35 PM UTC
    Flashblocks
    Timeline · 2 updates
    • investigating · Jun 02, 2026, 10:32 PM UTC

      Our team is currently investigating degraded broadcasting of Flashblocks on Base mainnet. We believe TX inclusion in final blocks is not affected.

    • resolved · Jun 22, 2026, 04:35 PM UTC

      The instability has been addressed and resolved. Node operators who were affected are recommended to upgrade to v1.1.1 of base/base which contains stability improvements and bug fixes: https://github.com/base/base/releases/tag/v1.1.1

    Latest: The instability has been addressed and resolved. Node operators who were affected are recommended to upgrade to v1.1.1 of base/base which contains stability improvements and bug fi…

See the full Base outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Base outage history →

Or sign up free to get alerts when Base breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 9 incidents View full outage history →