Hologram Outage History

Hologram partial outage · 1 active incident View live status →

Pingoru has recorded 55 incidents for Hologram: 51 in the last 12 months and 14 in the last 90 days.

Source: status.hologram.io

55incidents recorded
51last 12 months
14last 90 days
44 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct54%
Pingoru began tracking Hologram in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026229 of 720 (4%)
May 20263117 of 744 (16%)
June 20265114 of 720 (16%)
July 2026219 of 744 (3%)
August 20266147 of 744 (20%)
September 2026245 of 720 (6%)
October 20266284 of 525 (54%)

Incidents, newest first

Major October 21, 2026 Global-2 (8935 Prefix) Connectivity Issues 15h 13m Cellular network connectivity, SMS over cellular

Started Oct 21, 2026, 11:36 PM UTC· resolved Oct 22, 2026, 02:49 PM UTC

  1. investigating Oct 21, 2026, 11:36 PM UTC

    One of our partners is experiencing issues that is affecting the ability to connect and transmit cellular data. Hologram is working with our carrier partner to identify and address the issue. This is only affecting Global-2 SIMs with the prefix 8935. Other profiles are unaffected.

  2. resolved Oct 22, 2026, 02:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2026 G3 Service Disruption 5h 19m Cellular network connectivity

Started Oct 20, 2026, 02:03 PM UTC· resolved Oct 20, 2026, 07:23 PM UTC

  1. investigating Oct 20, 2026, 02:03 PM UTC

    We are currently investigating a possible service disruption affecting Global-3 profiles (ICCID prefix *89464) and their ability to create and maintain data sessions. We are working with our upstream providers to diagnose and resolve this issue, and will share more details as more information becomes available.

  2. resolved Oct 20, 2026, 07:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 15, 2026 Telus Outage affecting Canada Connectivity 5d 1h Cellular network connectivity, Cellular network connectivity, Cellular network connectivity, Cellular network connectivity

Started Oct 15, 2026, 06:04 PM UTC· resolved Oct 20, 2026, 07:25 PM UTC

  1. identified Oct 15, 2026, 06:04 PM UTC

    Telus has identified an issue with their network affecting new and existing connections. This outage is affecting all profiles connecting through Telus in Canada including CA-1, Global-1, Global-2, and Global-3. Other countries and networks are not affected.

  2. resolved Oct 20, 2026, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 9, 2026 Global-3 profiles unable to send or receive SMS on AT&T 5d 22h SMS over cellular

Started Oct 09, 2026, 04:52 PM UTC· resolved Oct 15, 2026, 03:24 PM UTC

  1. investigating Oct 09, 2026, 04:52 PM UTC

    We are currently investigating an issue where our Global-3 profiles cannot send or receive SMS messages when connected to AT&T. These same profiles do not have any issues with other networks. Data transfer remains unaffected. All other profiles remain unaffected.

  2. investigating Oct 09, 2026, 04:59 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Oct 14, 2026, 08:57 PM UTC

    A fix has been implemented and we are monitoring the results. Our tests are now all successful but devices might need to start a new data session before SMS can be successful.

  4. resolved Oct 15, 2026, 03:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 8, 2026 Duplicate data usage alerts issue –

Started Oct 08, 2026, 04:00 PM UTC· resolved Oct 08, 2026, 04:00 PM UTC

  1. resolved Oct 08, 2026, 04:54 PM UTC

    Alerts created for data limits or data warnings sent out an additional notification after an update to data limit functionality in our API. Paused SIMs were not affected by this change.

Read the full incident report →

Major September 23, 2026 Global-2 eUICC operations 18h 31m Hyper SIM eUICC Operations, SIM card operations

Started Sep 23, 2026, 09:33 PM UTC· resolved Sep 24, 2026, 04:05 PM UTC

  1. investigating Sep 23, 2026, 09:33 PM UTC

    We are currently experiencing a partial outage on our Global-2 profiles when performing some eUICC operations. We are actively working with our upstream partners to get this back to normal as soon as possible. Connectivity remains unaffected on Global-2 profiles. All other profiles remain unaffected along with their eUICC operations.

  2. investigating Sep 24, 2026, 02:01 PM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 24, 2026, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 3, 2026 Connectivity failures for devices on USA-2 (891480*) + Verizon on Global (894450*, 893571*, 894642*) 4h 16m Global Cellular Data Network

Started Sep 03, 2026, 09:51 PM UTC· resolved Sep 04, 2026, 02:08 AM UTC

  1. investigating Sep 03, 2026, 09:51 PM UTC

    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.

  2. resolved Sep 04, 2026, 02:08 AM UTC

    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.

Read the full incident report →

Minor August 31, 2026 Delayed Usage Reports in Dashboard 2h 6m Hologram website, Data Usage Reporting and Billing

Started Aug 31, 2026, 05:50 PM UTC· resolved Aug 31, 2026, 07:57 PM UTC

  1. monitoring Aug 31, 2026, 05:50 PM UTC

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

  2. monitoring Aug 31, 2026, 05:52 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Aug 31, 2026, 07:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2026 Elevated 2G/3G signaling failures on some networks in the Americas on Global-3 (G3) (ICCID Prefix 894642*) 9h 31m Global Cellular Data Network

Started Aug 27, 2026, 10:02 PM UTC· resolved Aug 28, 2026, 07:34 AM UTC

  1. investigating Aug 27, 2026, 10:02 PM UTC

    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.

  2. investigating Aug 27, 2026, 10:07 PM 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

  3. identified Aug 28, 2026, 12:50 AM UTC

    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.

  4. resolved Aug 28, 2026, 07:34 AM UTC

    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.

Read the full incident report →

Minor August 27, 2026 Degraded performance for large data transfers in the United States on Global-3 (G3) (ICCID Prefix 894642*) 5d 19h Global Cellular Data Network

Started Aug 27, 2026, 02:27 AM UTC· resolved Sep 01, 2026, 09:56 PM UTC

  1. investigating Aug 27, 2026, 02:27 AM UTC

    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.

  2. investigating Aug 27, 2026, 03:26 AM UTC

    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.

  3. investigating Aug 27, 2026, 04:39 PM 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.

  4. identified Aug 27, 2026, 04:40 PM 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.

  5. identified Aug 27, 2026, 06:55 PM 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.

  6. identified Aug 27, 2026, 11:53 PM UTC

    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.

  7. monitoring Aug 28, 2026, 11:29 PM UTC

    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.

  8. resolved Sep 01, 2026, 09:56 PM UTC

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

Read the full incident report →

Major August 25, 2026 Conductor API Service Disruption 3h 15m REST API, Hyper SIM eUICC Operations

Started Aug 25, 2026, 03:09 PM UTC· resolved Aug 25, 2026, 06:24 PM UTC

  1. investigating Aug 25, 2026, 03:09 PM UTC

    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.

  2. resolved Aug 25, 2026, 06:24 PM UTC

    This issue has been resolved

Read the full incident report →

Major August 25, 2026 USA-2 profile activations failing. Connectivity not impacted. 20h 32m SIM Card Administrative Operations

Started Aug 25, 2026, 12:38 AM UTC· resolved Aug 25, 2026, 09:11 PM UTC

  1. investigating Aug 25, 2026, 12:38 AM UTC

    We are currently investigating the issue. This does not impact connectivity for activated USA-2 profiles and only impacts the activation of new USA-2 profiles.

  2. resolved Aug 25, 2026, 09:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 15, 2026 Global-2 EU PoP service degradation 8h 58m Global Cellular Data Network, SMS over cellular - Device Terminated, SMS over cellular - Device Originated

Started Aug 15, 2026, 02:27 PM UTC· resolved Aug 15, 2026, 11:26 PM UTC

  1. identified Aug 15, 2026, 02:27 PM UTC

    We are experiencing service degradation on one of our Global-2 EU nodes, related to a cooling system outage at the site. Dedicated engineers are currently working to restore the affected infrastructure and service as quickly as possible. Other nodes in the same region, and in other regions remain unaffected. Other profiles are not affected.

  2. resolved Aug 15, 2026, 11:26 PM UTC

    This incident has been resolved. Service restoration was completed and all affected services have returned to normal operation.

Read the full incident report →

Minor July 24, 2026 Session Reporting 10m Data Usage Reporting and Billing

Started Jul 24, 2026, 12:40 PM UTC· resolved Jul 24, 2026, 12:51 PM UTC

  1. investigating Jul 24, 2026, 12:40 PM UTC

    There is currently an issue affecting session reporting in the dashboard. Updates for new sessions will not appear in the dashboard until this issue is resolved.

  2. investigating Jul 24, 2026, 12:50 PM UTC

    This issue has been resolved

  3. resolved Jul 24, 2026, 12:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 8, 2026 G3 Profile (ICCID prefix 89464*) State Change Workflow Disruption 18h 25m SIM Card Administrative Operations

Started Jul 08, 2026, 07:05 PM UTC· resolved Jul 09, 2026, 01:31 PM UTC

  1. investigating Jul 08, 2026, 07:05 PM UTC

    We are aware of and investigating an issue impacting the ability to change SIM state on G3 profiles. We've engaged our providers and will provide further information as soon as it becomes available

  2. resolved Jul 09, 2026, 01:31 PM UTC

    Our internal testing, and partner carriers have confirmed this issue to be resolved, thank you for your patience

Read the full incident report →

Minor June 20, 2026 Global 3 (8946 Prefix) Roaming Issues on US PoP 18h 20m Global Cellular Data Network

Started Jun 20, 2026, 12:46 AM UTC· resolved Jun 20, 2026, 07:07 PM UTC

  1. monitoring Jun 20, 2026, 12:46 AM UTC

    We are currently experiencing a disturbance on Roaming on our Global-3 profile (8946) in the US. The issue has been identified and a fix has been implemented, we are currently monitoring as we see traffic returning to normal levels.

  2. resolved Jun 20, 2026, 07:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 16, 2026 Delayed Usage Reporting G1 Carrier Profiles starting with 8944* 6h 53m Data Usage Reporting and Billing

Started Jun 16, 2026, 09:01 AM UTC· resolved Jun 16, 2026, 03:55 PM UTC

  1. investigating Jun 16, 2026, 09:01 AM UTC

    Hologram Engineers have identified an issue with the usage consumer from one of our carrier partners. We are investigating a fix. Connectivity is not affected. This is only impacting G1 Carrier Profiles starting with 8944*

  2. monitoring Jun 16, 2026, 09:34 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 16, 2026, 03:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026 New registrations and data sessions service disruption on Global-2 SIMs (8935* Prefix) 9h 3m Global Cellular Data Network

Started Jun 10, 2026, 05:37 AM UTC· resolved Jun 10, 2026, 02:40 PM UTC

  1. identified Jun 10, 2026, 05:37 AM UTC

    One of our upstream network partners is experiencing an outage affecting new registrations on their 2G, 3G, and 4G/LTE networks. We have notified the partner and are working with them to resolve this issue. This outage only affects SIM cards with the ICCID prefix 8935*.

  2. resolved Jun 10, 2026, 02:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 9, 2026 G2 Data Session Disruption in EU 22h 7m Global Cellular Data Network

Started Jun 09, 2026, 02:36 PM UTC· resolved Jun 10, 2026, 12:43 PM UTC

  1. investigating Jun 09, 2026, 02:36 PM UTC

    We are currently investigating a reported issue on our Global-2 profiles (ICCID prefix 89357*). Some devices might have trouble establishing or maintaining sessions. We are actively working with our upstream partners on a resolution and we'll provide updates as more information becomes available.

  2. resolved Jun 10, 2026, 12:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026 Delayed SIM State Changes on Global-1 Profiles (ICCID prefix 894450) 19h SIM Card Administrative Operations

Started Jun 02, 2026, 09:23 PM UTC· resolved Jun 03, 2026, 04:23 PM UTC

  1. investigating Jun 02, 2026, 09:23 PM UTC

    We are currently experiencing a backlog causing delays in SIM state changes for Global-1 profiles. Customers may experience longer than expected processing times when activating, deactivating, or pausing SIMs. We are unable to provide an estimated resolution time at this point, but we are actively working to clear the backlog. Cellular network connectivity and other API services are unaffected.

  2. resolved Jun 03, 2026, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 Intermittent connectivity on US2-profiles (ICCID prefix 89418) 5d 5h Global Cellular Data Network, SMS over cellular - Device Terminated, SMS over cellular - Device Originated

Started May 28, 2026, 04:48 PM UTC· resolved Jun 02, 2026, 09:52 PM UTC

  1. investigating May 28, 2026, 04:48 PM UTC

    We are seeing intermittent connectivity with some of our US2 profiles. Verizon is currently investigating the issue. All other profiles remain unaffected.

  2. resolved Jun 02, 2026, 09:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 18, 2026 Delayed SIM operations on Global-1 profiles (ICCID prefix 89445) 17h 13m SIM management dashboard, REST API, SIM Card Administrative Operations

Started May 18, 2026, 09:13 PM UTC· resolved May 19, 2026, 02:26 PM UTC

  1. investigating May 18, 2026, 09:13 PM UTC

    We are experiencing a delay on SIM card administrative operations (activations, plan changes, state changes) on our Global-1 profiles. Operations done through the Dashboard and API are impacted. Connectivity remains unaffected. All other profiles remain unaffected.

  2. resolved May 19, 2026, 02:26 PM UTC

    We are caught up on all delayed operations.

Read the full incident report →

Minor May 5, 2026 Partial Data Outage on Global-3 SIMs affecting 4G Services (8946* Prefix) 20h 29m Global Cellular Data Network

Started May 05, 2026, 12:42 AM UTC· resolved May 05, 2026, 09:11 PM UTC

  1. investigating May 05, 2026, 12:42 AM UTC

    One of our partners is experiencing issues that is affecting the ability to connect and transmit cellular data. Hologram is investigating an issue affecting 4G services globally, it may cause problems attaching to 4G networks and using 4G services. This only is affecting SIMs with the 8946* prefix.

  2. monitoring May 05, 2026, 01:03 AM UTC

    The issue has been identified and a fix was implemented. We are seeing traffic returning to normal levels.

  3. resolved May 05, 2026, 09:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 27, 2026 Delayed reporting on US2 profiles (ICCID prefix 89148) 1d 3h Data Usage Reporting and Billing

Started Apr 27, 2026, 09:11 PM UTC· resolved Apr 29, 2026, 12:32 AM UTC

  1. investigating Apr 27, 2026, 09:11 PM UTC

    Verizon is currently experiencing an issue where data usage/reporting is delayed on US2 profiles (Verizon-native). We are working with Verizon's team to get this resolved and the usage backfilled. We will provide updates as soon as we have further information. Reporting on all other profiles remains unaffected. Connectivity remains unaffected on all profiles.

  2. identified Apr 27, 2026, 09:37 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 29, 2026, 12:32 AM UTC

    The issue with delayed reporting has been resolved and data has been successfully backfilled.

Read the full incident report →

Critical April 16, 2026 API maintenance extended. 1h 13m SIM management dashboard, Events and Alerts, REST API, SMS over IP and 4 more

Started Apr 16, 2026, 12:56 PM UTC· resolved Apr 16, 2026, 02:10 PM UTC

  1. investigating Apr 16, 2026, 12:56 PM UTC

    We are currently investigating an issue with restoring the API services post-maintenance. We are working to restore services as soon as possible.

  2. identified Apr 16, 2026, 01:12 PM UTC

    We have identified the source of the issue extending maintenance and are currently implementing a fix.

  3. identified Apr 16, 2026, 01:25 PM UTC

    Services are coming back online as we continue to work on fixes.

  4. identified Apr 16, 2026, 01:37 PM UTC

    We are continuing to bring services back online.

  5. monitoring Apr 16, 2026, 01:44 PM UTC

    All services are restored and we are working through backlogs.

  6. resolved Apr 16, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →