Hologram Outage History

Hologram is up right now

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

Source: status.hologram.io

55incidents recorded
50last 12 months
14last 90 days
30 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct48%
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 20266286 of 592 (48%)

Incidents, newest first

Major October 9, 2025 Intermittent data sessions on G2 (89357*) 8d 6h Global Cellular Data Network

Started Oct 09, 2025, 07:31 PM UTC· resolved Oct 18, 2025, 01:31 AM UTC

  1. investigating Oct 09, 2025, 07:31 PM UTC

    We are investigating reports affecting a small subset of devices on G2. Impacted devices may experience shorter-than-expected session durations and occasional disconnections and reconnections We’ve engaged with upstream partners and are reviewing session handling to understand root cause.

  2. investigating Oct 10, 2025, 12:51 PM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 18, 2025, 01:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 9, 2025 Partial Outage - Global-1 SIMs/profiles (ICCID prefix 89445*) 18h 14m Global Cellular Data Network

Started Oct 09, 2025, 06:36 PM UTC· resolved Oct 10, 2025, 12:51 PM UTC

  1. investigating Oct 09, 2025, 06:36 PM UTC

    We're currently experiencing a partial outage on our cellular network specific to our G1 profiles (sims/profiles with ICCID prefix 89445*). Impact: • Some subscribers have difficulty attaching to LTE/2G/3G networks • Data and SMS services may be degraded or delayed The issue is currently escalated and we are investigating.

  2. monitoring Oct 10, 2025, 12:43 AM UTC

    Issue has been resolved, we will continue to monitor.

  3. resolved Oct 10, 2025, 12:51 PM UTC

    This incident has been resolved.

Read the full incident report →