PanelLaunch
Get started

What to Do When Your SMM Provider Goes Down

How to spot a failing provider early, the first-hour checklist, moving services to a backup provider, handling stuck orders, and setting up so the next outage barely matters.

Platform Admin 6 min read

On this page

Every SMM panel depends on providers it doesn't control. Sooner or later one of them stops delivering: orders sit in pending, the API returns errors, or a whole service category quietly stops starting. How you handle the next few hours decides whether customers stay.

This is a practical runbook: how to spot the problem early, what to do in the first hour, how to move services to a backup, and how to set up so the next outage is a non-event.

How to tell your provider is the problem

Before you change anything, confirm it is the provider and not your own setup. The usual signs:

  • Orders stay pending far longer than the service's normal start time, across many customers.
  • API errors when your panel sends orders or checks status, such as authentication failures, timeouts or "service not found".
  • Your balance with the provider stops moving, or drops to zero. A drained provider balance looks exactly like an outage to your customers.
  • Only one provider's services are affected while services from other providers work normally.

Check the simple causes first. Has your API key changed? Has the provider balance run out? Did the provider change a service ID? Live provider balances on your dashboard rule out the most common one in seconds.

The first hour

Work through this in order.

1. Stop new orders on the affected services. Disable or hide them so customers can't keep buying something that won't deliver. Every new order now is a future refund or complaint.

2. Check the provider's own channels. Most providers post outages in a Telegram channel or on their dashboard. Find out whether it is a short incident, a service change or something worse.

3. Tell your customers. A short announcement is enough: "Some Instagram services are delayed because of a provider issue. New orders are paused; existing orders will be completed or refunded." Customers forgive delays. They don't forgive silence.

4. Decide: wait or switch. If the provider says it will be back within hours and your customers aren't in a hurry, waiting is fine. If not, move the services.

Moving services to a backup provider

You can only switch quickly if a backup already exists. That's why it's worth connecting a second provider before you need it. Our guides on choosing a provider and adding providers and API keys cover the setup.

When you switch, map each service carefully. Two services with the same name can behave very differently. Compare:

  • Minimum and maximum quantity, and any quantity steps.
  • Start time and speed.
  • Refill and cancel support, and the refill period.
  • Link format: profile link versus post link.
  • Cost, so the new route doesn't sell below cost.

On a PanelLaunch Business panel, Smart Provider Replacement re-points services to new provider IDs in bulk, so moving a whole category is one operation rather than editing services one at a time. Business panels can also route each service to the cheapest provider with automatic failover, which handles many outages before you notice them.

A Child panel connects to one API provider. That keeps it simple and cheap, but it also means there is no backup to switch to. If uptime matters more to you every month, that is a good reason to move up to Business. Child Panel vs Main Panel explains the trade-off.

Handling orders that are already stuck

Orders placed before the outage need a decision, not just waiting:

  • Resend to the new provider if the old one never started them. Failed-order tools let you change the provider service ID and retry.
  • Cancel and refund orders the old provider can't complete. Refund to the customer's balance in full if nothing was delivered, or partially for the undelivered part.
  • Watch for double delivery. If the old provider recovers after you resent an order, the customer may receive twice. Cancel the old order with the provider where you can, or note it so you don't refund what was later delivered.

Profit protection matters here too. When you resend at a different provider, check that the new cost is still below the price the customer paid. Your panel's profit guard blocks orders that would sell below cost.

Our guide to reducing refunds and handling drops covers refund rules in more detail.

After the outage

When things are stable, do four quick things:

  1. Re-enable services you paused, or leave them on the backup if it performed better.
  2. Post a short update to customers saying service is back to normal.
  3. Write down what happened: which services, how long, what you did. Next time you'll move faster.
  4. Review your provider list. If one provider causes most of your incidents, reduce how much you depend on it.

Set up so the next outage barely matters

  • Use at least two providers for your best-selling services.
  • Keep balances topped up with every provider you rely on, and watch them daily.
  • Place small test orders on your backup routes now and then, so you know they work before you need them.
  • Keep a saved announcement ready to post in one click.
  • Keep refill and refund rules written down in your terms, so outage refunds follow a known policy. See SMM Panel Terms of Service and Refund Policy.

Frequently asked questions

How long should I wait before switching providers?

It depends on the service and your customers. For fast-moving services like views or likes, a few hours of delay is already a problem. For slower services, waiting for the provider's update is often fine.

Will customers lose their orders if I switch?

No, if you handle it properly. Orders that never started can be resent to the new provider, and orders that can't be completed are refunded to the customer's balance.

Can I prevent provider outages?

You can't stop a provider from failing, but you can make it matter less: two providers per key service, healthy balances, and routing with failover where your plan supports it.

The short version

Confirm the provider is the problem, pause affected services, tell your customers, then either wait or move the services to a backup you prepared earlier. Resend or refund stuck orders carefully, and use the incident to make the next one smaller.