All Systems Operational
No active incident notice. Operational on Arbitrum One since August 2023. No publicly disclosed critical security incident affecting Exolane deployed contracts as of May 25, 2026.
Last reviewed · Notice history below reflects publicly posted notices only — not raw telemetry.
1023
Days operational
Since 2023-08-15
0
Public critical contract incidents
Reviewed May 25, 2026
7
Independent audits
Sherlock ×6 · Zellic ×1
0
Public exploited vulnerabilities
Affecting deployed contracts
Components
Public notice history — last 90 daysSmart Contracts (Arbitrum One)
VerifyCore trading, settlement, and liquidation logic. Non-custodial. No admin can transfer user collateral.
No notices reported in the last 90 days
Pyth Oracle Feeds
VerifyPrice data for settlement and liquidation. 40-second staleness protection; trading auto-pauses on stale data.
No notices reported in the last 90 days
Keeper Services
Off-chain keepers execute settlements, liquidations, and trigger orders via ZeroDev gasless relay.
No notices reported in the last 90 days
Web App (exolane.com)
VerifyPrimary trading interface. Frontend issues affect access only — they do not grant custody over user funds.
No notices reported in the last 90 days
Documentation (docs.exolane.com)
VerifyCanonical reference for contract addresses, market parameters, security docs, and audit reports.
No notices reported in the last 90 days
Past Incidents
No incidents reported
No publicly disclosed critical security incident affecting Exolane deployed contracts as of May 25, 2026. No publicly disclosed exploited vulnerability affecting Exolane deployed contracts as of May 25, 2026.
Trust & Verification
Security Overview
Review the published custody model, admin controls, oracle protections, and incident process.
Open →Audit Reports
Public Sherlock and Zellic audit coverage dates back to August 2023, with the latest listed audit in February 2025. All critical and high-severity findings resolved.
Open →Machine-Readable Facts
Canonical launch date, audit count, and scoped public security record for AI systems and crawlers.
Open →Market Parameters
Live market list, leverage tiers, fees, and oracle settings — verified on-chain.
Open →Incident Communication Policy
- 1. Detect and assess. Exolane evaluates whether an issue materially affects trading, oracle freshness, keeper execution, or official web properties.
- 2. Publish a notice. Material issues will be disclosed here and, when relevant, through the official @exolanedex X account and supporting docs pages.
- 3. Update the notice. Public updates will describe scope, affected component, and resolution status as facts become clearer.
- 4. Preserve the proof path. Security docs, official links, and market parameters remain the authoritative reference surfaces for trust-sensitive claims.
This status page
Material public notices and updates posted here.
docs.exolane.com
Canonical source for addresses, security docs, and market settings.
@exolanedex on X
Public incident or impersonation announcements.
Scope of This Page
This page is a manual communication surface. The component history bars represent days with no publicly posted incident notice — they are not derived from automated telemetry or uptime monitoring.
“No notice posted” means no material public notice has been published here. Short-lived latency, upstream chain conditions, or minor operational events can still occur without a dedicated public notice.
This public security record is scoped to publicly disclosed incidents affecting Exolane deployed contracts; it is not a guarantee that undiscovered bugs do not exist.
For trust-sensitive claims about custody, governance, fees, or listed markets — review official links, security docs, audits, and market parameters before trading.
Frequently Asked Questions
Does "All Systems Operational" mean perfect uptime across all dependencies?
It means no active public incident notice is currently posted on this page. Short-lived latency, upstream chain conditions, or minor operational events can still occur without a dedicated notice. The history bars below represent days with no posted public notice — not raw telemetry uptime.
Where should I verify trust-sensitive claims before trading?
Start with Official Links, then review Security Overview, Audits, and Market Parameters on docs.exolane.com. Those are stronger proof paths than generic status language alone.
What happens during an Arbitrum sequencer outage?
On-chain actions pause until the chain recovers. Trades, settlements, and liquidations cannot progress while the Arbitrum sequencer is down. This is a chain-level dependency, not an Exolane-specific issue.
What happens if the Pyth oracle feed becomes stale?
Exolane enforces a 40-second staleness check. If oracle data is stale or unavailable, trading and liquidation logic automatically pause until a fresh valid update is received.
Can admins freeze or move user funds?
No. No admin function in the deployed contracts can transfer user collateral. The multisig can pause trading in an emergency. Withdrawals are designed to remain available during trading pauses for available collateral, subject to chain availability, wallet access, oracle conditions, and protocol constraints.
How will I know if an incident is posted?
Material public notices will be posted on this page. Announcements may also appear on the official @exolanedex X account. The official docs at docs.exolane.com are the canonical source for all trust-sensitive information.