Tokeny logo and current status indicator

Tokeny Incident History

Degraded

tokeny.com ↗5 top-level components

checked Oct 30, 2026 6:47 AM UTC · Tokeny's official status page

Tokeny is slower than normal.

Tokeny is experiencing degraded performance with some services running slower than normal.

Be the first to know

Statusfield watches Tokeny alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Tokeny incident history

6 reports published by Tokeny in the last 30 days · 1 still open

When Tokeny breaks, it is typically resolved in 5h 14m — median across 1 resolved incidents over 30 days.

October 29, 2026

Base network: delayed mainnet transaction inclusion

Ongoing · last update
  1. investigatingOct 29 · 17:07 UTC

    Base is investigating reports of slower than usual transaction inclusion on Base Mainnet; block production continues normally but some transactions may take longer to appear in a block or preconfirmation. We will post an update as more information becomes available. Upstream incident: https://base-l2.statuspage.io/incidents/7xj799fyhrlx

Reported by Tokeny on their status page.

October 9, 2026

Base network: mainnet withdrawal proposals halted

Last update
  1. resolvedOct 9 · 19:38 UTC

    Base mainnet proposal submission was halted earlier today, slowing in-flight withdrawals; the team identified the issue and proposals resumed under monitoring before the incident was fully resolved. No further impact is expected. Upstream incident: https://base-l2.statuspage.io/incidents/3sryt3zgjxxk

Reported by Tokeny on their status page.

Base network: mainnet withdrawal proposals halted

Last update
  1. ResolvedOct 9 · 19:38 UTC

    Base mainnet proposal submission was halted earlier today, slowing in-flight withdrawals; the team identified the issue and proposals resumed under monitoring before the incident was fully resolved. No further impact is expected. Upstream incident: https://base-l2.statuspage.io/incidents/3sryt3zgjxxk

Reported by Tokeny on their status page.

October 1, 2026

Base network: mainnet.base.org public RPC changes (Oct 8)

Last update
  1. resolvedOct 8 · 20:11 UTC

    Scheduled maintenance on mainnet.base.org public RPC (removal of debug/trace/txpool namespaces and lower read rate limits) has been completed as planned. No further action is needed; apps relying on these namespaces or higher throughput should use a dedicated RPC provider. Upstream incident: https://base-l2.statuspage.io/incidents/jrs0dpj60tqz

Reported by Tokeny on their status page.

Base network: mainnet.base.org public RPC changes (Oct 8)

Last update
  1. ResolvedOct 8 · 20:11 UTC

    Scheduled maintenance on mainnet.base.org public RPC (removal of debug/trace/txpool namespaces and lower read rate limits) has been completed as planned. No further action is needed; apps relying on these namespaces or higher throughput should use a dedicated RPC provider. Upstream incident: https://base-l2.statuspage.io/incidents/jrs0dpj60tqz

Reported by Tokeny on their status page.

September 24, 2026

Base network: scheduled Cobalt upgrade on Mainnet (Sep 30)

Last update
  1. resolvedSep 30 · 20:13 UTC

    Base completed the scheduled Cobalt upgrade to Base Mainnet, which began at 18:00 UTC and finished at 20:00 UTC on September 30th. No further action is needed; node operators should be running v1.4.2 or greater. Upstream incident: https://base-l2.statuspage.io/incidents/zctq4rtnmlxd

Reported by Tokeny on their status page.