> For the complete documentation index, see [llms.txt](https://upscalp.gitbook.io/upscalp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates.md).

# UpScalp Status and Service Updates

**Last reviewed:** 2026-05-23.

Use status updates to decide whether to fix your local setup, wait for a service-side update, or contact support with an account-specific report.

Check status updates when you need to know whether UpScalp is down, whether an incident applies to you, or whether the issue is more likely local setup.

Status updates tell you whether an UpScalp service is working normally, degraded, or interrupted. They do not tell you what is happening in the market or whether a setup is good.

## Check official sources first

Use:

1. Announcements: `https://t.me/upscalpannouncements`
2. Status notices linked from official UpScalp pages.
3. Support instructions only when official channels direct you there.

Do not rely on unofficial Telegram groups, DMs, or copied screenshots as the source of truth.

## Decide whether status applies to your issue

| Your issue                                       | Check status?                             | Also check                                                    |
| ------------------------------------------------ | ----------------------------------------- | ------------------------------------------------------------- |
| No UpScalp messages arrive for several users     | Yes.                                      | Announcements and the no-signals guide.                       |
| Only one Telegram account misses messages        | Yes, then local setup.                    | Telegram setup, plan access, and Premium verification.        |
| Premium verification failed                      | Only if an access incident is announced.  | Premium verification guide and support report format.         |
| A bot, link, or support account looks suspicious | No, unless an official warning is posted. | Official Links and account-protection guidance.               |
| Market is quiet and no signal appears            | Usually no.                               | Signal volume can be lower when valid setups are not present. |

If an issue affects only your account, a status page may not explain it. Run local setup and access checks before sending support a report.

## Read the status correctly

| Status        | Meaning                                     | What to do                                             |
| ------------- | ------------------------------------------- | ------------------------------------------------------ |
| Investigating | A problem is being checked.                 | Record your issue details; avoid repeated retries.     |
| Identified    | Cause is known and fix work is in progress. | Wait for the next update unless told to act.           |
| Monitoring    | A fix is live and being watched.            | Re-check your setup once, then wait if still affected. |
| Resolved      | Incident is closed.                         | Run local troubleshooting if your issue remains.       |

If no official status is posted, do not treat screenshots from other users as a service incident. Use the troubleshooting page and keep evidence in case support needs it.

## During an active incident

1. Do not restart setup repeatedly.
2. Do not submit the same support issue multiple times.
3. Keep UTC timestamps.
4. Follow only official instructions.
5. Do not create exchange API keys, share secrets, or enable withdrawal permissions because someone in an unofficial channel says it will fix the issue.

Repeated retries can make troubleshooting harder.

## After resolution

1. Confirm the affected plan: Lite, Premium, or approved beta.
2. Re-check Telegram delivery.
3. Run the no-signals guide if your account is still affected.
4. Contact support with timestamps if the issue persists.

Include the incident name or announcement timestamp in the report so support can separate post-incident cleanup from an unrelated account/setup issue.

## If your problem is not a service issue

Use these instead:

1. Telegram setup and notifications: [Set Up UpScalp Telegram Alerts](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)
2. Premium verification: [How to Complete UpScalp Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)
3. Official-link checks: [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)
4. Risk management: [Risk Management for UpScalp Signals](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)
5. Approved beta access: [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate)

If a page asks for account-specific details, use the support format instead of posting private details in a public channel.

## Related

1. [Signals Not Arriving](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals)
2. [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support)
3. [Telegram Setup](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)
4. [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)