Hypercare incident

[CA only] Interruption to all Hypercare services

Critical Resolved View vendor source →

Hypercare experienced a critical incident on March 29, 2026 affecting Login and Single Sign On (Canadian Region) and Messaging (Canadian Region) and 1 more component, lasting 20h 29m. The incident has been resolved; the full update timeline is below.

Started
Mar 29, 2026, 10:01 PM UTC
Resolved
Mar 30, 2026, 06:30 PM UTC
Duration
20h 29m
Detected by Pingoru
Mar 29, 2026, 10:01 PM UTC

Affected components

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)

Update timeline

  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.