Why is my eSIM stuck in pending status?

In sandbox, pending usually means the test carrier is simulating provisioning latency. In production, it means the carrier has not yet confirmed activation.

The short answer

pending

means the carrier has accepted the order but has not yet confirmed activation. In sandbox this is simulated and resolves within 10 seconds. In production it can take 30 seconds to 2 minutes depending on the carrier.

What to do

Try it yourself

Free sandbox. Real Tier-1 carriers. 60 seconds from signup to credentials.

Get started →

Do not re-create the eSIM. That creates a duplicate and consumes another plan credit.
Wait for the webhook. The
```
esim.activated
```
event fires the moment the carrier confirms.
Or poll, but no more than once every 5 seconds. Use the
```
GET /esims/{esimReference}
```
endpoint.

When it really is stuck

If an eSIM is still

pending

after 5 minutes in production, something is wrong. Check:

Carrier status page (linked from your dashboard)
The
```
errors[]
```
array on the eSIM resource
Your webhook endpoint is reachable (we retry, but you may be missing events)

Open a support ticket with the

esimReference

. We can see exactly where it is in the carrier pipeline.

Was this helpful?

Related help

Why is my eSIM stuck in pending status?

The short answer

What to do

Try it yourself

When it really is stuck

Related help

Can I reuse an esimReference across multiple plans?

What rate limits apply to bulk provisioning?

How do I get sandbox API credentials?