Hypercare Outage History

Hypercare partial outage · 1 long-running issue View live status →

Pingoru has recorded 141 incidents for Hypercare: 140 in the last 12 months and 5 in the last 90 days.

Source: status.us.hypercare.com

141incidents recorded
140last 12 months
5last 90 days
14 hourstypical duration
Incidents per month
0100200AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Hypercare 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 2026450 of 720 (7%)
May 202633 of 744 (0%)
June 202613 of 720 (0%)
July 2026108113 of 744 (15%)
August 20262143 of 744 (19%)
September 20262349 of 720 (49%)
October 202600 of 573 (0%)

Incidents, newest first

Minor July 8, 2026 Intermittent Delays – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    We sincerely apologize for any impact of the degraded performance incident may have caused your organization of the last few weeks. After monitoring the performance of our servers we've deduced that this incident has been resolved. Please be advised that a post mortem will be sent out by the end of this week to explain the technical issues our servers experienced along with the fix that was deployed. Impacted: Code Teams - Canadian Region

Read the full incident report →

Minor July 8, 2026 Intermittent latency / slowdown – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved. Impacted: Code Teams - Canadian Region

Read the full incident report →

Minor July 8, 2026 Login services (US and CA) and notification services (US) interruption – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved. Impacted: Login and Single Sign On - US Region, Messaging - US Region, Notifications and Real-Time Syncing - US Region

Read the full incident report →

Minor July 8, 2026 Messaging via Hypercare seems to be failing in the U.S. region – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    We are currently investigating this issue.

Read the full incident report →

Major July 8, 2026 Messaging web app and admin web app seems to be suffering downtime – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident is now resolved as Azure resolved their issues an hour ago.

Read the full incident report →

Minor July 8, 2026 Missing Config – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Missing Notifications – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    We have identified and resolved the issue. Notifications are back to normal.

Read the full incident report →

Minor July 8, 2026 Mobile application may experience slower response times – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    Incident was resulted from the disk drive running out of space. We have increased the capacity of our server that handles analytics, and everything is back up and running. There should have been little to no difference in user experience to the users on the mobile app. Hurray!

Read the full incident report →

Minor July 8, 2026 Not receiving realtime message events – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Notification delivery delayed – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Notifications Delayed – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    The issue has been resolved. The permissions for a role had been revoked which was preventing our servers from sending out notifications.

Read the full incident report →

Minor July 8, 2026 Notifications are failing – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Opening Hypercare on an iOS device resulting in a crash – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    Hypercare has currently pin pointed the issue to Instabug, the vendor we use to allow our users to report bugs. This issue is now resolved. Instabug was having issues resulting in downstream affects via Hypercare.The first detected crash of Hypercare resulting from this issue possibly is 07:50 am EST. We will be investigating whether this may result in a change of vendor or this can be preventable in the future.

Read the full incident report →

Major July 8, 2026 Organization Login (SSO) Outage for MGH – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 8, 2026 Our service is currently down due to issues experiencing in our analytics – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    The service is back up. Working towards ensuring this does not happen and it triggers alarms gracefully.

Read the full incident report →

Minor July 8, 2026 Performance Degradation – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    We sincerely apologize for any impact this incident may have caused you and your users. We will follow up with an email to explain the situation as well as the preventative measures that we will take going forward. Impacted: Code Teams - Canadian Region

Read the full incident report →

Minor July 8, 2026 Performance Degradation - SMS notification system – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Phone number escalation seems to be in a degraded performance – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    The phone escalations for code activations is now operational. One of our internal systems was updated which resulted this outage. We have added tickets to our backlog to implement safe guards to help prevent issues like this occurring in the future.

Read the full incident report →

Minor July 8, 2026 Potential slow loading times – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Push Notifications Affected during Migration – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Push Notifications, Emails, and SMS are slightly delayed – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Real-time updates are experiencing issues – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    The incident is now resolved, the issue is recognized. The notification server is going through an update that will resolve the issue for the future.

Read the full incident report →

Minor July 8, 2026 Reports of on-call and contacts not loading – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    At 18:40 eastern time, we got a support call that indicated on-call was not loading when clicking on the contacts. It was verified by us that it was also happening to us on the web platform and mobile.Our engineering team was escalated as P0 incident, and a recent change that was pushed out at 18:23 eastern time was reverted. The issue was resolved by 18:44 due to reverting a recent change.

Read the full incident report →

Minor July 8, 2026 Reports on notifications not being sent – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    We are confident the issue is fully resolved after monitoring the situation.

Read the full incident report →

Minor July 8, 2026 Resolved incident around inability to login post pin lock – Hypercare service

Started Jul 08, 2026, 08:07 PM UTC· resolved Jul 08, 2026, 08:07 PM UTC

  1. resolved Jul 08, 2026, 08:07 PM UTC

    Two days ago, a few of our users unfortunately could not get past the pin lock screen on iPhone to access their messages. Users who re-installed the app unfortunately did not result in addressing the issue. The only way support could have addressed it was ask the user to forget their pin which resulted in a log out. prior Given the limited amount of affected users, it was extremely difficult to pin down the root cause. After going through numerous edge cases, we were able to narrow down to authentication which was resulting in a bug where users would be presented with a infinite loading animation until timeout. We have addressed the issue with a patch from the backend that goes into affect immediately and will address the issue until the full fix is released from client in the next week. We apologize for this incident. This incident was not filed as we were unsure of the scale and the validity of the incident given the small amount of affected users. Given the affected user list was slowly growing, we quickly realize this was a critical issue and resolved it within 24 hours of realization.

Read the full incident report →