Is Gigs Down?

This incident is resolved. Our network provider has confirmed that the fix has been applied to all affected subscriptions. The plan changes that were stuck in pending since 10 November have been processed, restricted subscriptions affected by this issue have been restored, and new plan changes are being applied normally. We are reviewing the root cause together with our network provider. --- [2026-11-14T08:58:52Z] (monitoring) The fix from our network provider has been applied, and the plan changes that were stuck in pending since 10 November have now been processed. Restricted subscriptions affected by this issue have been restored, and new plan changes created today are being applied normally. We are now monitoring the situation and will follow up with a final update no later than 11:00 UTC. --- [2026-11-13T23:06:37Z] (identified) The network provider has applied a fix to all but one of the affected subscriptions. For all that have been corrected, the pending plan changes have been applied. We will continue monitoring the situation and working with the provider to remedy the last case. The next status update will come no later than 14 November, 08:00 UTC. --- [2026-11-13T19:01:06Z] (identified) Our network provider is applying a fix to the affected subscriptions. The fix is being rolled out in chronological order, starting with the subscriptions affected first, and we have confirmed on a first set of subscriptions that their pending plan changes are now applied. We expect the remaining subscriptions to be corrected over the coming hours. Once the fix is in place, we will reprocess the plan changes that are still pending. New activations remain unaffected. We will share the next update no later than 14 November, 08:00 UTC. --- [2026-11-13T16:43:29Z] (identified) We are seeing delays in processing subscription changes on p12. Since 10 November, some plan changes remain in pending and are not applied. Affected subscriptions may stay on their previous plan, and restricted subscriptions may not be restored. We have identified the cause together with our network provider and are working with them on a fix. New activations are not affected. We will share the next update no later than 19:00 UTC.

This issue is now resolved. Subscription actions on AT&T-backed lines are operating normally, and the backlog of queued requests has cleared. If you are still seeing a request that has not completed, please contact support and we will resolve it individually. --- [2026-11-09T16:58:42Z] (monitoring) A fix has been applied and service is recovering. Queued requests are now processing, and we expect the backlog to clear over the next period. If a request is still showing as failed or incomplete, please retry it now. We are continuing to monitor and will confirm once the backlog is fully cleared. --- [2026-11-09T16:36:58Z] (identified) We are aware of an issue affecting subscription actions on p11 AT&T-backed lines in the US. Since 13:46 UTC this is impacting activations, eSIM replacements, port-out credential generation, and subscription suspend and restore. Affected requests are queued and retrying automatically. There is no need to resubmit them, and resubmitting may add further delay. We have identified the cause and are working on a fix.

Between 09:21 and 09:31 UTC on October 12, **some API requests to retrieve and list subscriptions failed with HTTP 500 errors**. A request failed when it returned a subscription that was pending activation. A list request failed when one subscription in the result was pending activation. A recent change caused the errors. We rolled back the change at 09:30 UTC, and **the API recovered at 09:31 UTC**. Requests that failed during this period now succeed when you send them again. No production subscription data changed or was lost. No production create requests failed. **If you see an unexpected result from this period, please contact support.**