Is Tokeny down?

Last checked 3m ago
Current status
Tokeny is up

No incidents right now.

Official status page: https://status.tokeny.com · Polled every 5 minutes · 15 components tracked

Tokeny is operational right now. Last checked 3m ago; the most recent incident resolved 21h ago.

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

Users who monitor Tokeny also follow these Finance services: Affirm QuickBooks PayRange Avalara Plaid Xero Zuora Bill.com Xero Developer Platform Recharge View all 6,000+ providers
Tokeny uptime 99.78% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h
    Started Jul 28, 2026, 02:17 PM UTC · Resolved Jul 28, 2026, 03:17 PM UTC
    Timeline · 2 updates
    • 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

    Latest: 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…

  2. Resolved
    Started Jun 25, 2026, 06:46 PM UTC · Resolved Jun 25, 2026, 06:46 PM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 …

  3. Resolved
    Started Jun 25, 2026, 05:45 PM UTC · Resolved Jun 25, 2026, 05:45 PM UTC
    Timeline · 1 update
    • resolved · Jun 26, 2026, 04:12 AM UTC

      [Quicknode] Base Mainnet Block Production Disruption https://status.quicknode.com/incidents/mpft7mgzwmzp

    Latest: [Quicknode] Base Mainnet Block Production Disruption https://status.quicknode.com/incidents/mpft7mgzwmzp

  4. Resolved
    Started Jun 25, 2026, 05:45 PM UTC · Resolved Jun 25, 2026, 05:45 PM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 be…

Outage history

Past 90 days · 4 incidents View full outage history →