Is Gigs down?

Status: Resolved 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.

Status: Identified We are investigating a potential issue that resulted in unintentional deactivation of P15 addons. Affected components Roaming (p15) (Degraded performance)

Status: Identified We have identified the issue and are working on a fix. Affected components Roaming (p15) (Degraded performance)

Status: Identified The root cause of the incorrect addon deactivation has been resolved. We are currently applying mitigation measures to affected addons. Affected components Roaming (p15) (Degraded performance)

Status: Resolved Affected add-ons have been restored and all systems are functioning normally. Affected components Roaming (p15) (Operational)

Status: Investigating We are investigating a potential issue that may result in data allowances for a subset of P11 users being incorrectly reduced. Affected components United States (p11) (Degraded performance)

Status: Identified The root cause of the erroneous data reduction has been identified and resolved. We are currently applying mitigation measures to affected subscribers. Affected components United States (p11) (Degraded performance)

Status: Resolved Resolution measures have been completed for all affected subscribers. Affected components United States (p11) (Operational)

Status: Identified We are seeing degraded performance since 14:40 UTC for a subset of users on our P11 network while roaming outside of the United States. Domestic usage is not affected. Our engineering team has identified the root cause and is working on a resolution for the affected users. We will post the next update by 17:00 UTC, or sooner if the issue is resolved. Affected components United States (p11) (Degraded performance)

Status: Identified Service restoration is progressing as expected for the subset of users affected by this issue. Many of these users have already recovered, and restoration for the remaining users is being rolled out in waves. Overall service for users roaming on the P11 network remains unaffected outside of this subset. We will post the next update by 21:00 UTC, or sooner once restoration is complete. Affected components United States (p11) (Degraded performance)

Status: Monitoring Service restoration is progressing for the subset of affected users as expected. The majority of users have already recovered. Overall roaming service remains unaffected outside of this isolated group. Affected components United States (p11) (Degraded performance)

Status: Resolved This incident has been resolved. Roaming service was fully restored for all affected users as of 03:49 UTC, and performance has remained stable since. Affected components United States (p11) (Operational)

Status: Investigating We are seeing degraded performance for some API calls with one of our partner networks (p11) - activations may take longer to complete while this issue is ongoing. Affected components United States (p11) (Degraded performance)

Status: Resolved API performance has now returned to normal and activation performance is restored. Affected components United States (p11) (Operational)