Tokeny Outage History

Tokeny is up right now

Tokeny had 5 outages in the last 2 years totaling 310h 52m of downtime — averaging 0.2 incidents per month.

There were 5 Tokeny outages since January 26, 2026 totaling 310h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tokeny.com

Major October 9, 2026

Base network: mainnet withdrawal proposals halted

Detected by Pingoru
Oct 09, 2026, 02:12 PM UTC
Resolved
Oct 09, 2026, 07:38 PM UTC
Duration
5h 25m
Timeline · 3 updates
  1. investigating Oct 09, 2026, 02:12 PM UTC

    Base's team is investigating a stall in mainnet output root proposals, which is slowing down in-flight withdrawals from Base to Ethereum. We are monitoring the situation and will post updates as the team progresses. Upstream incident: https://base-l2.statuspage.io/incidents/3sryt3zgjxxk

  2. monitoring Oct 09, 2026, 02:43 PM UTC

    Base identified an issue that halted mainnet output root proposals, which slowed in-flight withdrawals; proposals have since resumed and the team is monitoring for stability. No action needed on our end at this time. Upstream incident: https://base-l2.statuspage.io/incidents/3sryt3zgjxxk

  3. resolved Oct 09, 2026, 07:38 PM 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

Read the full incident report →

Minor August 13, 2026

Internal service (primary-market-api) is down

Detected by Pingoru
Aug 13, 2026, 07:29 AM UTC
Resolved
Aug 25, 2026, 08:41 AM UTC
Duration
12d 1h
Affected: Servicing APIServicing API
Timeline · 2 updates
  1. investigating Aug 13, 2026, 07:29 AM UTC

    primary-market-api service is currently down at the moment. We're working to recover it as soon as possible.

  2. resolved Aug 25, 2026, 08:41 AM UTC

    primary-market-api service's situation has been resolved.

Read the full incident report →

Major July 28, 2026

Base network: mainnet safe head delayed (L1 batching)

Detected by Pingoru
Jul 28, 2026, 02:17 PM UTC
Resolved
Jul 28, 2026, 03:17 PM UTC
Duration
1h
Timeline · 2 updates
  1. identified Jul 28, 2026, 02:17 PM UTC

    Base's upstream status page reports that the Base Mainnet safe head is delayed: new block production is progressing normally, but data batching to Ethereum L1 is lagging. Services on Base remain operational, though L1-finalized (safe) state may be delayed until upstream resolves this. Upstream incident: https://base-l2.statuspage.io/incidents/j6y12tshwkcg

  2. resolved Jul 28, 2026, 03:17 PM UTC

    Base upstream has resolved the delayed mainnet Safe head; L1 data batching is progressing normally again. New block production was never interrupted, so Base transaction processing was unaffected — only finalization to Ethereum L1 was delayed. Upstream incident: https://base-l2.statuspage.io/incidents/j6y12tshwkcg

Read the full incident report →

Major June 25, 2026

Network issue Base mainnet - blockchain service degraded

Detected by Pingoru
Jun 25, 2026, 06:46 PM UTC
Resolved
Jun 25, 2026, 06:46 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 26, 2026, 05:12 AM UTC

    Base Mainnet Block Production Disruption Component: Base network connectivity Time: ~16:07 – 18:46 UTC, 25 Jun 2026 This was caused by an upstream Base Mainnet incident during the Beryl Upgrade activation, where a consensus problem caused an invalid block to be sequenced and halted block production. This is tracked by our RPC provider here: https://status.quicknode.com/incidents/mpft7mgzwmzp The node has since caught up and is fully in sync with the network. All Base services are operating normally. No action is required from users.

Read the full incident report →

Notice January 26, 2026

Technical Issue: Support Tickets Currently Unavailable

Detected by Pingoru
Jan 26, 2026, 12:14 PM UTC
Resolved
Jan 27, 2026, 03:27 AM UTC
Duration
15h 13m
Timeline · 2 updates
  1. investigating Jan 26, 2026, 12:14 PM UTC

    We are working to resolve a technical issue with our support system. We apologize, but any tickets created right now will not be recorded. Please check back soon.

  2. resolved Jan 27, 2026, 03:27 AM UTC

    This incident has been resolved.

Read the full incident report →