Tokeny Outage History

Pingoru has recorded 12 incidents for Tokeny: 7 in the last 12 months and 3 in the last 90 days.

12incidents recorded

7last 12 months

3last 90 days

45 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Tokeny in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Incidents, newest first

Started Oct 09, 2026, 02:12 PM UTC· resolved Oct 09, 2026, 07:38 PM UTC

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
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
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

Minor August 13, 2026 Internal service (primary-market-api) is down 12d 1h Servicing API, Servicing API

Started Aug 13, 2026, 07:29 AM UTC· resolved Aug 25, 2026, 08:41 AM UTC

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.
resolved Aug 25, 2026, 08:41 AM UTC

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

Started Jul 28, 2026, 02:17 PM UTC· resolved Jul 28, 2026, 03:17 PM UTC

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
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

Started Jun 25, 2026, 05:45 PM UTC· resolved Jun 25, 2026, 05:45 PM UTC

resolved Jun 26, 2026, 04:48 AM UTC

Base RPC node lagging behind network Component: Base network connectivity Time: ~17:45 – 18:15 UTC, 26 Jun 2026 Between approximately 17:45 and 18:15 UTC, our Base RPC node fell behind the public Base network. During this window, requests served from our Base endpoint may have returned stale on-chain data or experienced delays. The node has now caught up and is fully in sync with the network (within normal block tolerance). All Base services are operating normally. We are monitoring to ensure the node remains in sync. No action is required from users.

Started Jan 26, 2026, 12:14 PM UTC· resolved Jan 27, 2026, 03:27 AM UTC

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.
resolved Jan 27, 2026, 03:27 AM UTC

This incident has been resolved.