Tokeny Outage History
Tokeny degraded · 3 active incidents View live status →Pingoru has recorded 15 incidents for Tokeny: 10 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 2 | 3 of 720 (0%) |
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 1 | 289 of 744 (39%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 3 | 60 of 744 (8%) |
| November 2026 | 2 | 120 of 120 (100%) |
Incidents, newest first
Major October 29, 2026 Base network: delayed mainnet transaction inclusion 1d 23h
Started Oct 29, 2026, 05:07 PM UTC· resolved Oct 31, 2026, 05:05 PM UTC
- investigating Oct 29, 2026, 05:07 PM 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
- monitoring Oct 30, 2026, 07:34 PM UTC
A fix for delayed transaction inclusion on Base Mainnet has been deployed; blocks continued to be produced normally throughout, and early monitoring indicates the issue is resolved. We will continue monitoring conditions. Upstream incident: https://base-l2.statuspage.io/incidents/7xj799fyhrlx
- resolved Oct 31, 2026, 05:05 PM UTC
Base has resolved the earlier transaction inclusion delays on Base Mainnet; monitoring confirmed the fix was effective and block production was unaffected throughout. Upstream incident: https://base-l2.statuspage.io/incidents/7xj799fyhrlx
Major October 9, 2026 Base network: mainnet withdrawal proposals halted 5h 25m
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.
Major July 28, 2026 Base network: mainnet safe head delayed (L1 batching) 1h
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
Minor June 25, 2026 Network issue Base mainnet - blockchain service degraded –
Started Jun 25, 2026, 05:45 PM UTC· resolved Jun 25, 2026, 05:45 PM UTC
- resolved Jun 26, 2026, 04:12 AM UTC
[Quicknode] Base Mainnet Block Production Disruption https://status.quicknode.com/incidents/mpft7mgzwmzp
Major June 25, 2026 Network issue Base mainnet - blockchain service degraded 2h 39m
Started Jun 25, 2026, 04:07 PM UTC· resolved Jun 25, 2026, 06:46 PM UTC
- resolved Jun 25, 2026, 06:46 PM 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.
Notice January 26, 2026 Technical Issue: Support Tickets Currently Unavailable 15h 13m
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.