Hologram Outage History

Hologram is up right now

There were 9 Hologram outages since February 12, 2026 totaling 113h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hologram.io

Major April 27, 2026

Delayed reporting on US2 profiles (ICCID prefix 89148)

Detected by Pingoru
Apr 27, 2026, 09:11 PM UTC
Resolved
Apr 29, 2026, 12:32 AM UTC
Duration
1d 3h
Affected: Data Usage Reporting and Billing
Timeline · 3 updates
  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.

Detected by Pingoru
Apr 16, 2026, 12:56 PM UTC
Resolved
Apr 16, 2026, 02:10 PM UTC
Duration
1h 13m
Affected: Device DashboardData Engine and RoutesREST APISMS over IPSIM Card Administrative OperationsHyper SIM EUICC OperationsInbound Messaging APIData Usage Reporting and Billing
Timeline · 6 updates
  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 →

Minor March 25, 2026

Partial Global-2 Outage affecting SIMs with prefix 8935*

Detected by Pingoru
Mar 25, 2026, 10:35 AM UTC
Resolved
Mar 25, 2026, 04:45 PM UTC
Duration
6h 9m
Affected: Global Cellular Data NetworkSMS over cellular - Device TerminatedSMS over cellular - Device Originated
Timeline · 3 updates
  1. investigating Mar 25, 2026, 10:35 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. monitoring Mar 25, 2026, 01:51 PM UTC

    Our upstream partner has confirmed the outage has been resolved. We will be monitoring our metrics and provide updates accordingly.

  3. resolved Mar 25, 2026, 04:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026

Partial Global-3 (Prefix 8946*) Outage

Detected by Pingoru
Mar 25, 2026, 08:33 AM UTC
Resolved
Mar 25, 2026, 02:22 PM UTC
Duration
5h 49m
Affected: Global Cellular Data NetworkSMS over cellular - Device TerminatedSMS over cellular - Device Originated
Timeline · 3 updates
  1. investigating Mar 25, 2026, 08:33 AM UTC

    We are currently seeing issues with Global-3 (8946) devices attaching to the LTE network in the North American and Mexico regions. We are actively working to resolve this as soon as possible. This will only affect new sessions, existing sessions will not be affected.

  2. identified Mar 25, 2026, 10:50 AM UTC

    Our carrier partner is working on implementing a fix. With the fix in place the carrier is seeing traffic beginning to return to normal levels. We are continuing to investigate.

  3. resolved Mar 25, 2026, 02:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Backlog of usage reporting on Global-1 (ICCID prefix 89445*) profiles

Detected by Pingoru
Mar 18, 2026, 12:02 PM UTC
Resolved
Mar 19, 2026, 02:03 PM UTC
Duration
1d 2h
Affected: Data Usage Reporting and Billing
Timeline · 3 updates
  1. monitoring Mar 18, 2026, 12:02 PM UTC

    We are experiencing a backlog of incoming usage messages from our upstream provider on Global-1 profiles. Usage reporting in the Dashboard and API is currently delayed while the backlog is being processed. Usage reporting is not affected on any other profiles. Connectivity is not affected on any profiles.

  2. monitoring Mar 18, 2026, 06:31 PM UTC

    There is a fix in place. Engineering team is continuing to monitor.

  3. resolved Mar 19, 2026, 02:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026

Connectivity issues on Global-3 (G3) profiles (ICCID prefix 894642*)

Detected by Pingoru
Mar 12, 2026, 03:43 AM UTC
Resolved
Mar 12, 2026, 07:03 AM UTC
Duration
3h 20m
Affected: Global Cellular Data NetworkSMS over cellular - Device TerminatedSMS over cellular - Device Originated
Timeline · 3 updates
  1. investigating Mar 12, 2026, 03:43 AM UTC

    We are currently investigating a reported issue on our Global-3 (G3) profiles (ICCID prefix 894642*). We are seeing devices having trouble establishing and maintaining sessions on 4G/LTE. We are actively working with our upstream partners on a resolution and we'll provide updates as more information becomes available.

  2. monitoring Mar 12, 2026, 04:31 AM UTC

    Our metrics show traffic is returning to normal levels and we'll continue monitoring and update accordingly.

  3. resolved Mar 12, 2026, 07:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Connectivity issues on USA-2/Verizon profiles (ICCID prefix 89148*)

Detected by Pingoru
Feb 24, 2026, 04:13 AM UTC
Resolved
Feb 25, 2026, 05:01 AM UTC
Duration
1d
Affected: Global Cellular Data NetworkSMS over cellular - Device TerminatedSMS over cellular - Device Originated
Timeline · 5 updates
  1. investigating Feb 24, 2026, 04:13 AM UTC

    We are currently investigating a reported issue on our USA-2/Verizon profiles (ICCID prefix 89148*). We are seeing devices having trouble establishing and maintaining sessions on 4G/LTE. We are actively working with our upstream partners on a resolution and we'll provide updates as more information becomes available.

  2. monitoring Feb 24, 2026, 02:34 PM UTC

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

  3. monitoring Feb 25, 2026, 03:33 AM UTC

    Our metrics show that sessions and data transfer have stabilized to pre-incident levels. We are continuing to monitor for the time being for any further issues and will provide updates as needed.

  4. resolved Feb 25, 2026, 05:01 AM UTC

    This incident has been resolved.

  5. postmortem Mar 11, 2026, 08:46 PM UTC

    ## 1. Incident Summary On February 23rd, a subset of SIMs on Verizon-direct profiles experienced a loss of data connectivity. The disruption was caused by an APN misconfiguration applied to the subset of SIMs during a routine plan consolidation performed by Verizon. Affected devices were unable to pass data until the correct APN configurations were restored. ## 2. Root Cause Verizon performed a plan consolidation to streamline and clean up legacy plan configurations. During the provisioning process, a subset of SIMs was incorrectly migrated to a different APN than intended — specifically, devices were moved to a private APN when they should have remained on a public APN, or vice versa. This misconfiguration rendered the affected SIMs unable to establish data connectivity. ## 3. Timeline | Time \(UTC\) | Event | | --- | --- | | Feb 24, 00:00 | Service disruption first reported; data connectivity loss observed on affected SIMs | | Feb 24, 04:13 | Additional customer reports; status page posted | | Feb 24, 14:34 | Verizon identified root cause and began systematic remediation of affected SIM configurations | | Feb 24, 22:30 | Full service restoration initiated; Verizon actively correcting APN configurations on impacted SIMs | | Feb 25, 00:00 | Continued remediation of affected SIMs | | Feb 25, 03:33 | Metrics stabilized to pre-incident levels | | Feb 25, 05:01 | Incident resolved | ## 4. Impact Approximately 15,000 SIMs on Verizon-direct profiles, affecting only 0.1% of clients, were unable to pass data for the duration of the incident. No data loss or security impact was identified; the disruption was limited to connectivity availability. ## 5. Remediation Verizon corrected the APN configurations across all affected SIMs. Service was restored following the systematic re-application of the correct, validated APN settings to the impacted lines. ## 6. Preventative Measures Based on a post-incident review, the following controls have been implemented for all future Verizon plan migrations: * **Pre-deployment compatibility testing** is now required prior to executing any plan consolidation or migration affecting SIM configurations. * **Enhanced validation checkpoints** have been added to the provisioning process to verify APN configuration integrity before changes are applied at scale. Although testing was performed before making changes, this did not adequately prevent the issue. These measures are intended to prevent recurrence and ensure configuration accuracy during future planned changes.

Read the full incident report →

Minor February 20, 2026

Delayed SIM Operations on Global-1 SIMs

Detected by Pingoru
Feb 20, 2026, 10:17 PM UTC
Resolved
Feb 21, 2026, 01:13 AM UTC
Duration
2h 56m
Affected: SIM Card Administrative Operations
Timeline · 2 updates
  1. investigating Feb 20, 2026, 10:17 PM UTC

    There is a currently a backlog delaying SIM operations on some of the Global-1 profiles. Backlog is processing and some customers may experience delays. Cellular network and other API services are unaffected.

  2. resolved Feb 21, 2026, 01:13 AM UTC

    The backlog has been cleared.

Read the full incident report →

Minor February 12, 2026

Partial Global-2 (8935*) outage

Detected by Pingoru
Feb 12, 2026, 02:30 PM UTC
Resolved
Feb 13, 2026, 06:22 AM UTC
Duration
15h 52m
Affected: Global Cellular Data Network
Timeline · 3 updates
  1. investigating Feb 12, 2026, 02:30 PM 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. monitoring Feb 12, 2026, 04:28 PM UTC

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

  3. resolved Feb 13, 2026, 06:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Hologram downtime and outages?

Pingoru polls Hologram's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Hologram reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Hologram alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Hologram for free

5 free monitors · No credit card required