Hypercare Status - Canada

Hypercare Status - Canada

[CA Region Only] Intermittent Slowdown Issue

We have developed a fix for the issue, and it is currently undergoing validation and testing.

Pending successful testing, deployment to production is targeted for tonight. Mitigation measures remain in place to maintain service stability, and we will share our next update when the fix is released.


  • Oct 22, 2026 5:47 PM EDT · Monitoring

    We have developed a fix for the issue, and it is currently undergoing validation and testing.

    Pending successful testing, deployment to production is targeted for tonight. Mitigation measures remain in place to maintain service stability, and we will share our next update when the fix is released.

  • Oct 22, 2026 12:34 PM EDT · Monitoring

    The services are recovered. We have identified the potential cause for the downtime, and the engineers are actively working on applying a patch.

  • Oct 22, 2026 12:26 PM EDT · Investigating

    Services should be recovering now. We're investigating the root cause for the downtime.

Impacted: Messaging - Canadian Region, Viewing Who is On-Call - Canadian Region, Login and Single Sign On - Canadian Region, +7 more

System Status

Jan 16, 1904 - Apr 14, 1904

Messaging - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Viewing Who is On-Call - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Login and Single Sign On - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Notifications and Real-Time Syncing - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

File Attachments - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Virtual Pager - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Code Teams - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Administration and Scheduling - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

Self-serve Scheduling - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904

API & Integrations - Canadian Region

· --% uptime
Jan 16, 1904
Apr 14, 1904
Loading components…
Incident history