All Systems Operational
Last checked:
100.0%
6-month average uptime
Current Status
Trading Engine
Core matching and position management on Arbitrum One smart contracts.
Oracle Feed (Pyth Network)
Real-time price feeds with on-chain staleness protection (40 s grace period).
Settlement & Liquidation
Keeper-driven settlement, liquidation, and funding-rate application.
Order Execution
Limit orders, stop-loss, and take-profit execution via keeper network.
Frontend Application
Next.js trading interface served on Arbitrum One.
API & Subgraph
REST and GraphQL endpoints for market data, positions, and history.
Uptime — Last 6 Months
Oct 2025 – Mar 2026| Month | Uptime | Downtime | Incidents |
|---|---|---|---|
| Oct 2025 | 100.00% | 0 h 0 m | None |
| Nov 2025 | 100.00% | 0 h 0 m | None |
| Dec 2025 | 100.00% | 0 h 0 m | None |
| Jan 2026 | 100.00% | 0 h 0 m | None |
| Feb 2026 | 100.00% | 0 h 0 m | None |
| Mar 2026 | 100.00% | 0 h 0 m | None |
Incident History
No incidents reported
Exolane has maintained continuous operation with zero service interruptions since October 2025. All smart contract operations, oracle feeds, and keeper services have performed within expected parameters.
Infrastructure
Blockchain
Arbitrum One (Chain ID: 42161). All trading logic runs in audited smart contracts.
Oracle
Pyth Network price feeds with 40-second staleness protection. Trading pauses automatically if prices go stale.
Keepers
Automated settlement, liquidation, and order execution services monitoring all markets continuously.
Monitoring
Datadog APM, RUM (Real User Monitoring), and custom alerting for latency, errors, and oracle health.
How We Measure Uptime
Uptime is measured across all monitored components: smart contract availability on Arbitrum, oracle price feed freshness, keeper service health, frontend responsiveness, and API latency.
A component is considered operational when it responds within expected latency bounds and produces correct results. Degraded performance means the service is functional but slower than normal. An outage means the component is unavailable or producing incorrect results.
Blockchain-level downtime (e.g. Arbitrum sequencer outages) is tracked separately and disclosed. Exolane smart contracts cannot operate during sequencer downtime, but this is an L2 infrastructure dependency, not an Exolane service failure.
Frequently Asked Questions
Is Exolane currently operational?
Yes. All systems — trading engine, oracle feed, settlement, order execution, frontend, and API — are fully operational as of the date shown above.
What is Exolane's historical uptime?
Exolane has maintained 100% uptime across all monitored services for the last 6 months (October 2025 – March 2026), with zero reported incidents.
Has Exolane ever had a security incident?
No. As of March 2026, Exolane has not experienced any security incidents, exploits, or loss of user funds. Smart contracts have been audited 7 times by Sherlock and Zellic.
What happens during an Arbitrum sequencer outage?
During sequencer downtime, no on-chain transactions process — including trades, settlements, and liquidations. This is an Arbitrum L2 infrastructure dependency. Exolane resumes normal operation instantly when the sequencer recovers.