Public Status & Service Notices
This page is a public notice board for Exolane. It explains core dependencies, where material incident notices should appear, and how to verify official information before trading. It is not a live uptime dashboard.
Last reviewed:
Current public notice
No active incident notice is currently published on this page.
Absence of a notice here is not a guarantee of perfect uptime or live telemetry.
Verification Path
Official Links
Use the official domain, contact, and core contract list as your root of trust.
Open sourceSecurity Overview
Review the published custody model, admin controls, oracle protections, and incident process.
Open sourceAudits
Read the public audit lineage and linked reports for the cited Perennial V2 codebase.
Open sourceMarket Parameters
Check the published live market list, leverage tiers, fees, and oracle settings.
Open sourceCore Dependencies
Arbitrum One
Core trading logic runs in smart contracts on Arbitrum One.
If the sequencer or chain is unavailable, new on-chain actions, settlements, and liquidations pause until the chain recovers.
Pyth Network
Oracle updates determine settlement and liquidation pricing.
If oracle data is stale or unavailable, trading and liquidation logic wait for a fresh valid update.
Keeper Network
Keepers execute settlement, liquidation, and trigger-order flows.
Keeper degradation can lengthen pending windows or delay automation, even when contracts remain deployed and user funds remain non-custodial.
Web App And Docs
The frontend and docs are the primary user interface and reference surface.
Frontend or API issues can affect access and visibility, but they do not grant custody over user funds.
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 should be disclosed here and, when relevant, through the official X account and supporting docs pages.
- 3. Update the notice. Public updates should describe scope, affected dependency, and resolution status as facts become clearer.
- 4. Preserve the proof path. Security docs, official links, and market parameters remain the stronger reference surfaces for trust-sensitive claims than generic marketing copy.
This status page
Material public notices and follow-up updates should be posted here when relevant.
Official Links and docs
The docs remain the canonical place to verify domains, addresses, security docs, and market settings.
@exolanedex
Public incident or impersonator announcements may also appear on the official X account.
What This Page Does And Does Not Mean
This page is a manual communication surface. It is useful for public notices, dependency mapping, and trust-path links, but it does not prove real-time service health by itself.
No notice posted here should be read only as the absence of an active public notice on this page, not as a claim of perfect uptime, zero latency, or universal health across every dependency.
Users should still review official links, security docs, audits, and market parameters before trading, especially when checking trust-sensitive claims about custody, governance, fees, or listed markets.
Frequently Asked Questions
Is this a real-time uptime dashboard?
No. This page is a manual public notice board. It explains dependencies, where notices will appear, and how to verify official Exolane information.
Does no notice on this page mean every component is perfectly healthy?
No. It only means there is no active public incident notice currently posted here. Short-lived latency, upstream chain conditions, or minor operational issues can still occur without a dedicated notice.
Where should I verify trust-sensitive claims before trading?
Start with Official Links, then review Security Overview, Audits, and Market Parameters. Those pages are the stronger proof path than generic status language alone.
What happens during an Arbitrum sequencer outage?
On-chain actions pause until the chain recovers. Because Exolane depends on Arbitrum for execution, trades, settlements, and liquidations cannot progress while the sequencer is down.