Hypercare Outage History

Hypercare is up right now

Hypercare had 28 outages in the last 2 years totaling 1067h 43m of downtime — averaging 1.2 incidents per month.

There were 28 Hypercare outages since June 12, 2025 totaling 1067h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hypercare.com

Major May 3, 2026

[US] Service interruption to Hypercare services

Detected by Pingoru
May 03, 2026, 03:03 AM UTC
Resolved
May 03, 2026, 03:27 AM UTC
Duration
23m
Affected: Login and Single Sign On (U.S. Region)Virtual Pager (U.S. Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (U.S. Region)Viewing Who is On-Call (U.S. Region)Code Teams (U.S. Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (U.S. Region)API & Integrations (U.S. Region)
Timeline · 3 updates
  1. identified May 03, 2026, 03:03 AM UTC

    A service interruption has been identified impacting real time notifications to the Hypercare platform. This issue is caused by maintenance work from Hypercare's cloud services provider. An update is expected in the next 10 minutes.

  2. monitoring May 03, 2026, 03:06 AM UTC

    Services are restored and we are continuing to monitor.

  3. resolved May 03, 2026, 03:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 3, 2026

[CA] Service interruption to Hypercare services

Detected by Pingoru
May 03, 2026, 01:36 AM UTC
Resolved
May 03, 2026, 03:27 AM UTC
Duration
1h 51m
Affected: Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)
Timeline · 5 updates
  1. identified May 03, 2026, 01:36 AM UTC

    A service interruption has been identified impacting real time notifications to the Hypercare platform. This issue is caused by maintenance work from Hypercare's cloud services provider. An update is expected in the next 10 minutes.

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

    Real time notifications are restored and we are continuing to monitor the issue.

  3. identified May 03, 2026, 02:21 AM UTC

    Partial interruption to services are being experienced due to maintenance work on Hypercare's cloud services provider. Intermittent interruptions may be experienced in the next 5-10 minutes.

  4. monitoring May 03, 2026, 02:30 AM UTC

    All core services are now operational and we are continuing to monitor.

  5. resolved May 03, 2026, 03:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026

Intermittent latency / slowdown

Detected by Pingoru
Apr 20, 2026, 11:04 PM UTC
Resolved
Apr 21, 2026, 12:27 AM UTC
Duration
1h 23m
Affected: Login and Single Sign On (Canadian Region)Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)Self-serve Scheduling (Canadian Region)Virtual Pager (Canadian Region)
Timeline · 3 updates
  1. monitoring Apr 20, 2026, 11:04 PM UTC

    We are monitoring intermittent slowdown / latency in the Hypercare platform on both web and mobile platforms.

  2. investigating Apr 20, 2026, 11:09 PM UTC

    We are investigating the root cause of intermittent slowdowns / latency interrupting Hypercare services.

  3. resolved Apr 21, 2026, 12:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 16, 2026

Unplanned service interruption to all Hypercare services

Detected by Pingoru
Apr 16, 2026, 04:36 PM UTC
Resolved
Apr 17, 2026, 05:45 PM UTC
Duration
1d 1h
Affected: Login and Single Sign On (Canadian Region)Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)Self-serve Scheduling (Canadian Region)Administration and Scheduling (Canadian Region)API & Integrations (Canadian Region)Virtual Pager (Canadian Region)
Timeline · 5 updates
  1. investigating Apr 16, 2026, 04:36 PM UTC

    We are currently investigating an unplanned interruption to all Hypercare services

  2. monitoring Apr 16, 2026, 05:06 PM UTC

    Services have resumed. We are continuing to monitor services to ensure return to full operations. Mobile app users are encouraged to check their Hypercare app to ensure they have remained logged into the platform.

  3. monitoring Apr 16, 2026, 05:17 PM UTC

    We are continuing to monitor login issues reported on the Web platform

  4. monitoring Apr 16, 2026, 05:21 PM UTC

    Login services have resumed on the web platform. We are continuing to monitor services to ensure return to full operations.

  5. resolved Apr 17, 2026, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 15, 2026

Web Client real-time web sockets not connecting

Detected by Pingoru
Apr 15, 2026, 10:42 PM UTC
Resolved
Apr 16, 2026, 06:33 PM UTC
Duration
19h 50m
Affected: Notifications and Real-Time Syncing (Canadian Region)
Timeline · 3 updates
  1. identified Apr 15, 2026, 10:42 PM UTC

    An issue has been identified with Hypercare's Web Client platform where incoming messages are not appearing in real-time until a refresh of the page. Outgoing messages are sending to recipients and sending messages is not impacted.

  2. monitoring Apr 15, 2026, 11:01 PM UTC

    We have corrected a configuration error with our Domain Name System (DNS). If users of the Web Client platform are still experiencing a 'Reconnecting' banner, you will need to do a hard refresh of your browser (press Ctrl + Shift + R on your keyboard) to clear the cache. Note, depending on device and network configurations, DNS updates may take up to 24 hours to be implemented.

  3. resolved Apr 16, 2026, 06:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 10, 2026

[US only] Interruptions to services

Detected by Pingoru
Apr 10, 2026, 02:41 PM UTC
Resolved
Apr 10, 2026, 08:33 PM UTC
Duration
5h 52m
Affected: Login and Single Sign On (U.S. Region)Virtual Pager (U.S. Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (U.S. Region)Viewing Who is On-Call (U.S. Region)Code Teams (U.S. Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (U.S. Region)API & Integrations (U.S. Region)
Timeline · 3 updates
  1. investigating Apr 10, 2026, 02:41 PM UTC

    There is currently an unplanned downtime to all Hypercare service in the US region. We are currently investigating the issue.

  2. monitoring Apr 10, 2026, 03:04 PM UTC

    A fix has been implemented and services are operational. We're continuing to monitor Hypercare services.

  3. resolved Apr 10, 2026, 08:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 29, 2026

[CA only] Interruption to all Hypercare services

Detected by Pingoru
Mar 29, 2026, 10:01 PM UTC
Resolved
Mar 30, 2026, 06:30 PM UTC
Duration
20h 29m
Affected: Login and Single Sign On (Canadian Region)Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)Self-serve Scheduling (Canadian Region)Administration and Scheduling (Canadian Region)API & Integrations (Canadian Region)Virtual Pager (Canadian Region)
Timeline · 8 updates
  1. investigating Mar 29, 2026, 09:44 PM UTC

    We are currently experiencing downtime to all Hypercare services. The team is investigating the issue.

  2. monitoring Mar 29, 2026, 10:01 PM UTC

    All services are operational. We have identified the issue and we're closely monitoring.

  3. monitoring Mar 29, 2026, 10:25 PM UTC

    The schedule tab on web client and admin portal is not loading. Our team is investigating.

  4. monitoring Mar 29, 2026, 10:36 PM UTC

    We observed increased connections to our database which is causing issues. Users might experience intermittent errors or a longer loading time when using the application. We're monitoring the issue.

  5. monitoring Mar 30, 2026, 12:24 AM UTC

    All services are operational. We're monitoring the issue.

  6. monitoring Mar 30, 2026, 12:37 AM UTC

    We are noticing an inconsistent delivery for real time messages. Push notifications are not impacted. We're restarting the services.

  7. monitoring Mar 30, 2026, 01:11 AM UTC

    Services are back to operational. We will share a post-mortem shortly.

  8. resolved Mar 30, 2026, 06:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 9, 2026

[US Only] Push Notification Delivery Issue

Detected by Pingoru
Mar 09, 2026, 12:07 AM UTC
Resolved
Mar 09, 2026, 12:14 AM UTC
Duration
7m
Affected: Notifications and Real-Time Syncing (U.S. Region)
Timeline · 2 updates
  1. investigating Mar 09, 2026, 12:07 AM UTC

    We are currently investigating an alert that the push notification service is experiencing errors. Our engineering team is attempting to restore the service.

  2. resolved Mar 09, 2026, 12:14 AM UTC

    Our engineering team has restored the service. Post mortem will be posted once it is available.

Read the full incident report →

Notice March 8, 2026

[US only] Push notifications are not being delivered on Hypercare

Detected by Pingoru
Mar 08, 2026, 01:22 PM UTC
Resolved
Mar 08, 2026, 02:29 PM UTC
Duration
1h 6m
Affected: Notifications and Real-Time Syncing (U.S. Region)
Timeline · 4 updates
  1. investigating Mar 08, 2026, 01:22 PM UTC

    We are currently investigating an issue affecting users' ability to receive push notifications on the U.S. server. We are actively working to identify the cause, and are exploring multiple paths to resolution. We apologize for any inconvenience this is causing for users.

  2. investigating Mar 08, 2026, 01:25 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 08, 2026, 01:46 PM UTC

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

  4. resolved Mar 08, 2026, 02:29 PM UTC

    This incident is fully resolved. Our team will continue to monitor to ensure this incident does not occur again.

Read the full incident report →

Critical March 7, 2026

[US only] Authentication failing on Hypercare

Detected by Pingoru
Mar 07, 2026, 01:52 AM UTC
Resolved
Mar 08, 2026, 01:22 PM UTC
Duration
1d 11h
Affected: Login and Single Sign On (U.S. Region)Virtual Pager (U.S. Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (U.S. Region)Viewing Who is On-Call (U.S. Region)Code Teams (U.S. Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (U.S. Region)API & Integrations (U.S. Region)
Timeline · 4 updates
  1. investigating Mar 07, 2026, 01:52 AM UTC

    We have confirmed reports that authentication is not working on U.S. which will affect all users using Hypercare in the U.S. region. We are currently investigating the cause and hope to restore the service as soon as possible.

  2. investigating Mar 07, 2026, 03:07 AM UTC

    Partial recovery of core services have returned (Messaging, Login, On-Call Scheduling). Real-time notifications remain non-operational.

  3. monitoring Mar 07, 2026, 04:09 AM UTC

    All core services are now operational. The team is monitoring to ensure continue stability.

  4. resolved Mar 08, 2026, 01:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 6, 2026

[US only] Interruption to all Hypercare services

Detected by Pingoru
Mar 06, 2026, 05:10 PM UTC
Resolved
Mar 07, 2026, 04:07 AM UTC
Duration
10h 57m
Affected: Login and Single Sign On (U.S. Region)Virtual Pager (U.S. Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (U.S. Region)Viewing Who is On-Call (U.S. Region)Code Teams (U.S. Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (U.S. Region)API & Integrations (U.S. Region)
Timeline · 4 updates
  1. investigating Mar 06, 2026, 05:10 PM UTC

    We are currently investigating reports of an unplanned interruption to all core services in the US region.

  2. monitoring Mar 06, 2026, 05:48 PM UTC

    Core services resumed. We are continuing to monitor the incident.

  3. monitoring Mar 06, 2026, 10:04 PM UTC

    This incident has been resolved. We apologize for the interruption to services and will share a post mortem shortly.

  4. resolved Mar 07, 2026, 04:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 4, 2026

[Canada only] Unplanned interruption to services

Detected by Pingoru
Mar 04, 2026, 05:57 PM UTC
Resolved
Mar 06, 2026, 04:30 AM UTC
Duration
1d 10h
Affected: Login and Single Sign On (Canadian Region)Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)Self-serve Scheduling (Canadian Region)Administration and Scheduling (Canadian Region)API & Integrations (Canadian Region)Virtual Pager (Canadian Region)
Timeline · 5 updates
  1. investigating Mar 04, 2026, 05:57 PM UTC

    We are currently investigating an unplanned downtime of all core services for users in Canada.

  2. monitoring Mar 04, 2026, 06:44 PM UTC

    A fix has been implemented and core services have returned. We are continuing to monitor the incident.

  3. identified Mar 04, 2026, 07:14 PM UTC

    We are observing intermittent latency in push notifications and real-time syncing of messages on web client. We're monitoring the system performance closely.

  4. monitoring Mar 04, 2026, 09:06 PM UTC

    A fix has been implemented. Real time notification and syncing are operational. We are monitoring the performance.

  5. resolved Mar 06, 2026, 04:30 AM UTC

    Core services have resumed and remained stable for the past 24 hours. The team is continuing to monitor push notification and web socket events for real-time syncing. The team has continued to disable the automated status reset feature to maintain a stable environment. The automated status reset feature has been running intermittently in a controlled environment to ensure users status’ are reset appropriately.

Read the full incident report →

Major March 4, 2026

[Canada only] Intermittent interruption to push notification service

Detected by Pingoru
Mar 04, 2026, 08:57 AM UTC
Resolved
Mar 04, 2026, 09:57 AM UTC
Duration
59m
Affected: Notifications and Real-Time Syncing (Canadian Region)
Timeline · 4 updates
  1. investigating Mar 04, 2026, 08:57 AM UTC

    We are currently investigating an issue with push notifications impacting users in Canada. Push notifications are being reported as delivering intermittently to users of the Hypercare mobile app and web platform.

  2. investigating Mar 04, 2026, 09:24 AM UTC

    We are continuing to investigate an issue with push notifications impacting users in Canada. Users of the Hypercare mobile and web platform are receiving intermittent push notifications. Messages to physical pagers have also been identified as being impacted by this issue.

  3. monitoring Mar 04, 2026, 09:30 AM UTC

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

  4. resolved Mar 04, 2026, 09:57 AM UTC

    This incident has been resolved. A postmortem will be posted shortly.

Read the full incident report →

Major March 3, 2026

[Canada and US] Directory Synchronization Feature Temporarily Disabled

Detected by Pingoru
Mar 03, 2026, 06:34 AM UTC
Resolved
Mar 30, 2026, 08:26 PM UTC
Duration
27d 13h
Affected: API & Integrations (Canadian Region)API & Integrations (U.S. Region)
Timeline · 2 updates
  1. identified Mar 03, 2026, 06:34 AM UTC

    We have temporarily disabled the Directory Synchronization feature (automatic user provisioning and deprovisioning) in both Canada and US regions, as it has been identified that configuration adjustments are needed to ensure the feature operates in full capacity within our new cloud environment. A fix is underway and a full sync will be ran against applicable organizations when the feature is re-enabled. For users that need to be on an on-call schedule prior to the fix being released, organization administrators are advised to create accounts manually for users via the Admin Portal (admin.hypercare.com). Alternatively, you may contact Hypercare Support ([email protected] or 1(877) 379-3533) for advice on next steps. Users can continue to log into their organizations with Single Sign-On (SSO), if enabled. SSO is not impacted by this incident.

  2. resolved Mar 30, 2026, 08:26 PM UTC

    Directory Synchronization has been enabled. Following the deployment of a fix on March 26, we have completed the following recovery steps: - Full Synchronization: All Active Directory records were resynced between March 26-28 to ensure data accuracy. - Real-time Updates: Webhooks are now active and capturing directory changes (adds, moves, and changes) as they occur. - Final Phase: We are currently finalizing the enablement for a small subset of organizations with specific shared-account configurations. Organization administrators have been sent a detailed briefing regarding their specific sync status. If you have immediate questions, please contact [email protected].

Read the full incident report →

Critical March 2, 2026

[CA region only] Unplanned interruption to services

Detected by Pingoru
Mar 02, 2026, 04:25 PM UTC
Resolved
Mar 02, 2026, 06:35 PM UTC
Duration
2h 10m
Affected: Login and Single Sign On (Canadian Region)Messaging (Canadian Region)Notifications and Real-Time Syncing (Canadian Region)File Attachments (Canadian Region)Viewing Who is On-Call (Canadian Region)Code Teams (Canadian Region)Self-serve Scheduling (Canadian Region)Administration and Scheduling (Canadian Region)API & Integrations (Canadian Region)Virtual Pager (Canadian Region)
Timeline · 5 updates

Read the full incident report →

Major February 25, 2026

[US and Canada] Virtual pagers with custom audio handling files are not operating

Detected by Pingoru
Feb 25, 2026, 04:20 PM UTC
Resolved
Feb 25, 2026, 07:00 PM UTC
Duration
2h 39m
Affected: Virtual Pager (U.S. Region)Virtual Pager (Canadian Region)
Timeline · 3 updates
  1. identified Feb 25, 2026, 04:20 PM UTC

    An issue has been identified for virtual pager users who have a custom audio files handling the initial greeting, and if applicable, the voicemail instructions. Outside calls to virtual pager numbers who have custom audio files will encounter a muffled sound or no sound when calling the number and will not be able to proceed to leave a callback number. This is impacting all users in Canada and US regions. The interim solution is to have the audio file be updated to Hypercare's default audio messages, which can be done via the Admin Portal at admin.hypercare.com. Alternatively, designated administrators can call Hypercare Support at 1(877) 379-3533 to have this updated. We are actively working on a permanent fix.

  2. identified Feb 25, 2026, 06:59 PM UTC

    Virtual pager users who had custom audio file(s) handling the initial greeting, and if applicable, the voicemail instructions, set up on their virtual pager prior to February 24 should now have their paging services restored. We are working on a fix impacting the upload of new custom audio files.

  3. resolved Feb 25, 2026, 10:32 PM UTC

    Virtual paging services were restored to normal operations at 13:59 ET

Read the full incident report →

Major February 25, 2026

[Canada only] Shifts generated from 3rd-party schedule integration partners not appearing in Hypercare

Detected by Pingoru
Feb 25, 2026, 10:14 AM UTC
Resolved
Feb 26, 2026, 01:46 AM UTC
Duration
15h 31m
Affected: API & Integrations (Canadian Region)
Timeline · 3 updates
  1. identified Feb 25, 2026, 10:14 AM UTC

    An issue has been identified regarding shifts not populating in Hypercare for departments that leverage a third-party schedule integration partner (MetricAid and Mesh AI), which is impacting users in Canada. If there are any changes that need to be made to the current on-call shift(s), schedule/department admins will need to make these updates directly in Hypercare's Admin Portal (admin.hypercare.com) to ensure the correct information appears in Hypercare. A fix is being worked on. Next update is expected for 12:00 PM or sooner. After the fix is deployed, schedule information will be re-synced to ensure data is accurate in Hypercare.

  2. identified Feb 25, 2026, 06:34 PM UTC

    We are continuing to work on a fix for this issue. If there are any changes that need to be made to the current on-call shift(s), schedule/department admins will need to make these updates directly in Hypercare's Admin Portal (admin.hypercare.com) to ensure the correct information appears in Hypercare.

  3. resolved Feb 26, 2026, 01:46 AM UTC

    This issue has been resolved.

Read the full incident report →

Notice December 14, 2025

[US Region only] Reports of few users with SAML errors when attempting to login

Detected by Pingoru
Dec 14, 2025, 04:18 PM UTC
Resolved
Dec 14, 2025, 07:03 PM UTC
Duration
2h 45m
Affected: Login and Single Sign On (U.S. Region)
Timeline · 5 updates
  1. investigating Dec 14, 2025, 04:18 PM UTC

    We have several users who have indicated issues logging into Hypercare.

  2. investigating Dec 14, 2025, 05:03 PM UTC

    We are still investigating this issue as it is only affecting a subset of our customer. We are identifying the cause of this issue.

  3. investigating Dec 14, 2025, 06:26 PM UTC

    Based on our investigation, it seems to point to us that this issue is limited to a small subset of users limited to a single organization which could be caused by a misconfiguration on the customers' need. We are attempting to coordinate with IT at the organization to identify the issue.

  4. monitoring Dec 14, 2025, 07:03 PM UTC

    The incident was isolated: Our investigation confirms that this Single Sign-On (SSO) issue was strictly limited to the two users who reported it and did not affect our general user base. False Alarms: Although our system initially flagged potential errors for other users, follow-up checks confirmed these were false positives, and no other customers were experiencing issues. We have identified the cause of these false alerts and are implementing a fix. Next Steps for Affected Users: The problem affecting the two original users is most likely due to a misconfiguration of SSO on the customer's IT side. We are currently working with our partner to confirm this diagnosis and resolve the issue.

  5. resolved Dec 14, 2025, 07:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025

[CA and US Region] Virtual Pager Alerts

Detected by Pingoru
Nov 18, 2025, 01:22 PM UTC
Resolved
Nov 18, 2025, 04:45 PM UTC
Duration
3h 23m
Affected: Virtual Pager (U.S. Region)Virtual Pager (Canadian Region)
Timeline · 3 updates
  1. investigating Nov 18, 2025, 01:22 PM UTC

    We're receiving an increased number of virtual pager error alerts. We are investigating which numbers are impacted.

  2. monitoring Nov 18, 2025, 03:00 PM UTC

    The increased alerts between 7-8am ET are related to the Cloudflare outage (https://www.cloudflarestatus.com/), which has caused a downstream impact on our virtual pager services. The virtual pagers are operational and we're monitoring.

  3. resolved Nov 18, 2025, 04:45 PM UTC

    This incident is resolved.

Read the full incident report →

Minor November 13, 2025

[US Region only] Inconsistent Push Notification

Detected by Pingoru
Nov 13, 2025, 06:16 PM UTC
Resolved
Nov 13, 2025, 07:29 PM UTC
Duration
1h 13m
Affected: Notifications and Real-Time Syncing (U.S. Region)
Timeline · 3 updates
  1. investigating Nov 13, 2025, 06:16 PM UTC

    We have received reports on inconsistent push notification delivery in the US region. It might result in users receiving back up SMS. We're currently investigating this issue.

  2. monitoring Nov 13, 2025, 06:28 PM UTC

    A fix has been implemented and we're currently monitoring.

  3. resolved Nov 13, 2025, 07:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 29, 2025

Ongoing service interruptions from scheduled maintenance period

Detected by Pingoru
Oct 29, 2025, 09:00 AM UTC
Resolved
Nov 06, 2025, 07:40 PM UTC
Duration
8d 10h
Affected: Login and Single Sign On (Canadian Region)Login and Single Sign On (U.S. Region)Virtual Pager (U.S. Region)Messaging (Canadian Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (Canadian Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (Canadian Region)File Attachments (U.S. Region)Viewing Who is On-Call (Canadian Region)Viewing Who is On-Call (U.S. Region)Code Teams (Canadian Region)Code Teams (U.S. Region)Self-serve Scheduling (Canadian Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (Canadian Region)Administration and Scheduling (U.S. Region)API & Integrations (Canadian Region)API & Integrations (U.S. Region)Virtual Pager (Canadian Region)
Timeline · 15 updates

Read the full incident report →

Minor October 28, 2025

[CA Region, Web Portal] User Contact Page Not Loading

Detected by Pingoru
Oct 28, 2025, 10:20 AM UTC
Resolved
Oct 28, 2025, 03:50 PM UTC
Duration
5h 29m
Affected: Login and Single Sign On (Canadian Region)Viewing Who is On-Call (Canadian Region)
Timeline · 5 updates
  1. investigating Oct 28, 2025, 10:20 AM UTC

    [CA Region, Web only] The web application in Canada region is having the below issues: - Login via single-sign-on. Logged in users are advised to stay logged in - Viewing the contact profile details of users. Searching users is impacted Mobile users are not impacted. The engineers are currently investigating the issues.

  2. identified Oct 28, 2025, 12:24 PM UTC

    [Canada Region] The engineers are working on a hot fix for the web SSO login issue, as well as user profile viewing and searching.

  3. identified Oct 28, 2025, 01:20 PM UTC

    [Canada Region] User profile viewing and searching is fixed. Engineers are working on fixing the SSO login issue.

  4. monitoring Oct 28, 2025, 02:39 PM UTC

    [Canada region] The fix for SSO login on web browser has been deployed. Users are now able to login to their Hypercare accounts.

  5. resolved Oct 28, 2025, 03:50 PM UTC

    The incident is resolved and closing this incident.

Read the full incident report →

Critical October 28, 2025

[US Region Only] Scheduled Maintenance Downtime Extended

Detected by Pingoru
Oct 28, 2025, 09:04 AM UTC
Resolved
Oct 28, 2025, 08:30 PM UTC
Duration
11h 26m
Affected: Login and Single Sign On (U.S. Region)Messaging (U.S. Region)Notifications and Real-Time Syncing (U.S. Region)File Attachments (U.S. Region)Viewing Who is On-Call (U.S. Region)Code Teams (U.S. Region)Self-serve Scheduling (U.S. Region)Administration and Scheduling (U.S. Region)API & Integrations (U.S. Region)
Timeline · 9 updates

Read the full incident report →