Check the availability of Lovely Legends platform services, including trading, market data, wallet services, deposits, withdrawals, API, Telegram Mini App, and website access.
Overall status
Running checks against public endpoints…
Current checks are based on public endpoint reachability and may not represent full backend health. Full incident tracking and historical uptime reporting are part of our transparency roadmap.
Every badge on this page is produced by a request your own browser makes, right now, to a public endpoint — nothing here is hand-edited and no uptime figure is published. Checks run against https://llapi.lflabs.fund and this site, and they repeat automatically every 60 seconds while the page is open. Because they run from your device, they also reflect what your own network can reach.
Each card rolls up the service group of the same name below it. Rows that cannot be checked from a signed-out browser are excluded from the verdict and counted separately, so a tile never claims coverage it does not have.
25 services in 6 groups. Each card names the endpoint it checked and when it last produced a result.
The matching engine and the order flow that runs on top of it.
Listed markets and their trading gates, read from the live registry.
EndpointGET /exchange/pairs
What this check proves: Proves the market registry is being served and which markets are open. It does not place an order, so it does not prove an order would fill.
The order-matching core behind every market.
EndpointMonitoring setup pending
Matching can only be proven by placing a real order against a real book, which would move real funds. This page will not do that. The Order Book and Recent Trades checks below are the closest public evidence that the engine is running: both are published by it.
Submitting, amending and cancelling orders.
EndpointMonitoring setup pending
Order routes sit behind authentication and would need a signed-in account and a live balance to exercise. Check from inside the app or the Mini App.
Live depth published for LF/USDT.
EndpointGET /exchange/orderbook?pair=LF/USDT
What this check proves: An empty book is a market with no resting orders, not a fault — the depth figures are reported here rather than graded.
The public trade tape for LF/USDT.
EndpointGET /exchange/market-trades?pair=LF/USDT
What this check proves: A quiet market legitimately returns no recent trades. The check is that the tape is being served, not that it is busy.
The prices, candles and market lists the website, the app and integrators read.
Last price and 24h statistics for LF/USDT.
EndpointGET /exchange/ticker?pair=LF/USDT
OHLC candles behind every chart on the site and in the app.
EndpointGET /exchange/candles?pair=LF/USDT&timeframe=1h
What this check proves: Checks that candles are served for the 1h timeframe. It does not verify the values, and it does not check every timeframe.
The listed-market table with 24h high, low, volume and trade count.
EndpointGET /exchange/markets/leaderboard
The aggregate price feed used across the platform.
EndpointGET /price/all
Balances, deposits and withdrawals. Most of this is behind your account.
Your balances, portfolio value and transaction history.
EndpointMonitoring setup pending
Every wallet route is tied to a signed-in account, so nothing about it can be checked from a signed-out browser without inventing a result.
The assets and networks currently accepting deposits.
EndpointGET /deposit/supported-coins
What this check proves: Proves the deposit configuration is being served and which networks are open. Crediting a deposit depends on chain confirmations and on the network itself, neither of which is measured here.
Per-asset withdrawal gates published in the market registry.
EndpointGET /exchange/pairs
What this check proves: Reads the public gate — whether withdrawals are enabled for an asset. Submitting and signing a withdrawal happens behind authentication and is not exercised from this page.
Balances updating after a trade, transfer, deposit or reward.
EndpointMonitoring setup pending
Balance updates are account-scoped and only observable while signed in. If a balance looks stale, reload the app before contacting support.
The operator review a withdrawal passes before it is signed.
EndpointMonitoring setup pending
This is a human review step, not a service with an endpoint, so it has no machine-checkable state. A request sitting at Pending is waiting for that review; nothing is wrong with it.
The public market-data surface and the streaming feed integrators build on.
The API gateway that serves every documented public endpoint.
EndpointGET /
What this check proves: Checks the gateway itself. The individual market-data endpoints it serves are checked one by one in the groups above.
Authenticated trading endpoints for market makers and integrators.
EndpointMonitoring setup pending
Private endpoints require an IP-bound API key pair. Probing them from a public page would need a live key, so they are deliberately not checked here.
Streaming market data, checked by subscribing to a public channel.
Endpointwss://…/ws — subscribe to a public depth channel
What this check proves: A socket that opens and then says nothing is treated as a failure — this check waits for a frame on the channel it subscribed to.
The public endpoint reference served by this site.
EndpointGET /api
The ways into the platform: this website, Telegram, and sign-in.
llx.lflabs.fund — this site. If you can read this, it is serving.
EndpointGET /manifest.webmanifest
The app shell served to Telegram clients at ll.lflabs.fund.
EndpointGET https://ll.lflabs.fund/
What this check proves: Confirms the host answered. Whether Telegram itself is reachable from your network is outside anything this page can measure.
The sign-in page for the browser app at /login.
EndpointGET /login
What this check proves: Checks that the sign-in page is served. The Telegram and email sign-in exchanges are not run — a probe would create a real login attempt.
Profile, security options and connected accounts.
EndpointMonitoring setup pending
Account screens exist only behind a signed-in session.
Self-service guides and the routes to a person.
Guides for deposits, withdrawals, trading, security and verification.
EndpointGET /help
How accounts are protected and how to avoid impersonation scams.
EndpointGET /security
Telegram and email support.
EndpointMonitoring setup pending
Support runs on Telegram and email. Neither can be probed from a browser, and a page that guessed would be guessing about the channel you use when something has already gone wrong.
Incident history reporting is being prepared as part of Lovely Legends’ transparency roadmap. When a disruption affects trading, transfers or access, it will be recorded here with the time it started, the services involved and what changed afterwards.
Planned maintenance updates will appear here before scheduled platform work, naming the services affected and the expected window. Deposits and withdrawals on an affected network may be paused during that time.
We are improving platform transparency step by step. More detailed uptime history, incident reports, and maintenance updates will be added as the exchange grows. Nothing below is live today, and each card says so.
Checks that run on a schedule from outside the browser, so a result exists even when nobody has the page open.
Internal health signals from the matching engine, settlement and the chain watchers, reported alongside the public endpoint checks on this page.
Availability measured over time and published per service. Until that data has been collected, no uptime figure appears anywhere on this page.
A dated record of disruptions with updates as they are worked, and what changed afterwards so the same fault is not repeated.
Planned work announced here before it starts, with the affected services and the expected window named up front.
Opt-in alerts so you learn about a disruption without having to remember to open this page.
Use Check again at the top of this page. The checks run from your own browser, so a result can change simply because your connection did.
Find the service in the groups above and open View details. It names the endpoint that was checked and what a result on that endpoint does and does not prove.
A request that looks like it failed may have been accepted. Submitting it again can create a second withdrawal or a second order rather than retrying the first. Check your transaction or order history before trying anything twice.
Many things that look like an outage are answered there — pending withdrawal reviews, deposits waiting on chain confirmations, and network-specific requirements such as memo tags. Start with Deposits or Withdrawals.
Use the routes listed on this page and no others. Include the coin, network, amount and time of the request — that is what makes a specific transfer findable.
Lovely Legends support will never ask for your password, private key, seed phrase, Telegram login code, email verification code, or remote access to your device. Anyone who does is not us — end the conversation and report it.
Official routes: t.me/john_lflabs and support@lflabs.fund. Read the security guides before acting on any message that claims to be from us.