How our systems are running today
This page is an informational summary of the SQARME CMD components and the third-party services they rely on. It is not a real-time monitor and does not state a guaranteed uptime — for live alerts and incident updates we use Telegram and email.
01Current status
The components below make up SQARME CMD. We review and publish their status here; treat it as a human-maintained summary rather than an automated, real-time monitor.
This is an informational summary, not a real-time status monitor. The indicators above reflect our latest review as of 16 July 2026 and do not represent continuous automated monitoring or any guaranteed level of availability. Inside the dashboard, your own engine reports its live state — verifying, recovering, connected or disconnected — which is the most accurate signal for your account.
02Upstream dependencies
SQARME CMD is software that automates your own Binance account, so it relies on several third-party services. An outage or degradation at any of these can affect your experience even when our own systems are healthy. Each provider operates its own status page and policies, which govern those services.
| Dependency | What it powers | If it is degraded |
|---|---|---|
| Binance | P2P trading, order data and counterparty details | Orders, balances and releases may stall or fail |
| Telegram | Approvals, alerts and notifications | Approvals and alerts may be delayed |
| UPI / bank rails | Counterparty payments (incl. eRupee, IMPS, bank transfer) | Payments may be slow to settle or fail to verify |
| Google (Cloud Vision & Fonts) | Receipt OCR and web fonts | OCR verdicts or page styling may be affected |
Please check the relevant provider's own status page during any disruption that appears to originate outside SQARME. We have no control over these services and cannot guarantee their availability.
03Scheduled maintenance
From time to time we perform planned maintenance — security updates, infrastructure changes or feature rollouts. We aim to announce planned maintenance in advance through Telegram and email so you can plan around it.
- Most maintenance is performed with no interruption to live trading.
- Some changes require an engine restart. When your engine restarts, it returns to a locked state and you may need to log in again with your email, master password and TOTP code.
- Restarting the control plane or web layer does not log you out of your engine; only an engine restart does.
04How we communicate incidents
When an incident affects SQARME CMD, we keep you informed directly rather than relying on you to refresh a dashboard:
- Telegram — the primary channel for real-time alerts. Make sure your account is linked (you set this up with a 6-digit code on first login) so you receive these messages.
- Email — used for advance notice of planned maintenance and for follow-ups on significant incidents.
If you believe you are experiencing an issue that is not reflected on this page, please report it using the details below — your report helps us confirm and communicate the scope quickly.
05Report an issue
To report a problem, contact us and include as much detail as you can so we can investigate without delay:
- Your registered email / username.
- What you were doing and what you expected to happen.
- The engine status shown in your dashboard (
verifying,recovering,connectedordisconnected). - The time (with IST) it occurred and any on-screen error message or screenshot.
- care@sqarme.com
- Phone & WhatsApp
- +91 99903 22528
- Support hours
- Mon–Fri, 10 AM – 6 PM IST
Still need a hand?
Our team replies Mon–Fri, 10 AM – 6 PM IST.