Is Hologram down?

We are investigating reports of devices on the USA-2 profile losing connectivity in the United States, beginning at approximately 2:10 PM CT (19:10 UTC) on September 3, 2026. This may also affect data roaming on the Verizon network for Global profiles.

Between approximately 2:10 PM CT and 4:20 PM CT (19:10 to 21:20 UTC) on September 3, 2026, some devices on Verizon network lost connectivity in Arkansas, northern Mississippi, Oklahoma, and western Tennessee. The cause was a fiber cut affecting the Verizon network in those areas. Verizon has resolved the issue, and impacted devices have returned to service. No changes were required on the Hologram platform.

There is an ongoing analytics platform outage that is impacting our reporting. We expect recovery within 1hr.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are investigating an increase in signaling failures on 2G and 3G networks with our Global-3 carrier partner. Impact appears concentrated in North and South America and affects several operators across multiple countries. Affected devices may fail to attach or register or may see repeated attach retries on 2G/3G. Devices attaching over LTE, LTE-M, or NB-IoT are not currently affected. The disturbance began at 2026-08-27 20:30 UTC.

We are seeing that traffic on the following networks may be impacted by this issue. This may not be an exhaustive list. Affected devices may fail to attach or register or may see repeated attach retries on 2G/3G. Devices attaching over LTE, LTE-M, or NB-IoT are not currently affected. Canada, Bell Canada, Rogers Canada, TELUS Mexico, Telcel Mexico, AT&T USA, Verizon USA, T-Mobile USA, AT&T Jamaica, Flow Thailand, AWN India, Vodafone

The carrier partner has traced this to an internal link failure affecting several roaming partners. One of the affected links has been restored, and signaling has returned to normal for devices on Vodafone India and AWN Thailand. Work continues on the remaining affected links. We can also confirm that SK Telecom in South Korea is impacted by this issue.

This incident is resolved. Signaling has been stable across all affected operators since 2026-08-28 02:30 UTC, and extended monitoring has confirmed full recovery. The disruption ran from 2026-08-27 20:30 UTC to 2026-08-28 02:30 UTC, a total of 6 hours. The cause was an internal link failure at an upstream carrier used by several of Global-3 network roaming partners.

We are investigating reports of degraded data performance affecting devices in the United States (AT&T, T-Mobile, and Verizon) on our Global-3 (G3) profile SIMs (ICCID prefix 894642*). Affected devices are attaching normally and maintaining data sessions, but transfers involving larger payloads are seeing significantly reduced throughput and elevated failure rates. Sessions passing small amounts of data appear to be unaffected. We have engaged our network partners and dedicated engineers are actively investigating. Devices outside the United States are not currently believed to be impacted. The next update will be provided within 60 minutes, or sooner if we have new information.

We are continuing to investigate this issue and there is no new information at this time. We will provide the next update when new information is available.

We have identified the cause of the degraded data performance affecting a subset of devices in the United States. An MTU mismatch in the network path is causing packet loss for affected sessions, which presents as failed or unusually slow transfers, particularly for uploads. Devices may be affected intermittently, and devices on the same account or in the same location may behave differently. This affects Global-3 devices in the United States across AT&T, T-Mobile, and Verizon. Sessions on other profiles and in other regions are not impacted. We are working with our upstream network partner on remediation. We will provide the next update by 19:00 UTC.

We have identified the cause of the degraded data performance affecting a subset of devices in the United States. An MTU mismatch in the network path is causing packet loss for affected sessions, which presents as failed or unusually slow transfers, particularly for uploads. Devices may be affected intermittently, and devices on the same account or in the same location may behave differently. This affects Global-3 devices in the United States across AT&T, T-Mobile, and Verizon. Sessions on other profiles and in other regions are not impacted. We are working with our upstream network partner on remediation. We will provide the next update by 19:00 UTC.

No new information is available at this time as work continues to remediate this issue. We will provide another update within the next 2 hours, if not sooner.

A temporary mitigation is in place and affected devices should see some improvement. This is a partial measure and does not fully resolve the issue. Transfers involving large packets may continue to fail or run slowly. Work continues with our upstream network partners on both an immediate fix and a permanent resolution.

A fix has been applied and data performance for affected devices in the United States has returned to expected levels. We are monitoring to confirm performance remains stable.

Our monitoring has confirmed the network is performing within normal parameters. We continue to work with network partners on future prevention and optimization.

We are currently investigating an issue where Conductor API services are unavailable, impacting eUICC operations on active SIMs. Non-Conductor related API endpoints remain unaffected.

This issue has been resolved