Home
/
Status
/
Service
Healthcare communication and coordination platform for clinical teams.
Source
auto
Category
Communication
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 22m ago
28
Components
0
Active incidents
0
Maintenance
4.76%
90d uptime
[Canada Region] Service slowdown to Hypercare services
Jun 1, 1:43 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 28 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Canadian Region Related to all the services available in the Canadian Region | Operational | Group | Not recorded |
United States Region Related to all the services available in the U.S. Region | Operational | Group | Not recorded |
App Store Availability | Operational | Group | Not recorded |
Google Play Store This component will advise if the Hypercare app is available to download in the Google Play Store. | Operational | Component | Not recorded |
Login and Single Sign On (Canadian Region) - Login with or without Single Sign On (SSO) - Signup with or without Single Sign On (SSO) - Single Sign On include but not limited to LDAP, Active Directory, Google Sign In, and others | Operational | Component | Not recorded |
Login and Single Sign On (U.S. Region) - Login with or without Single Sign On (SSO) - Signup with or without Single Sign On (SSO) - Single Sign On include but not limited to LDAP, Active Directory, Google Sign In, and others | Operational | Component | Not recorded |
Apple App Store This component will advise if the Hypercare app is available to download in the Google Play Store. | Operational | Component | Not recorded |
Virtual Pager (U.S. Region) - Virtual Pager associated with users, roles, code teams - Voicemail recordings | Operational | Component | Not recorded |
Messaging (Canadian Region) - Sending Hypercare messages - Message statuses (sent, delivered, read) - Sending HyperForms (formerly Hypercare Templated Messages) | Operational | Component | Not recorded |
Messaging (U.S. Region) - Sending Hypercare messages - Message statuses (sent, delivered, read) - Sending HyperForms (formerly Hypercare Templated Messages) | Operational | Component | Not recorded |
Twilio Voice, North America | Operational | Component | Not recorded |
Marketing Website (Global) Any web pages for marketing purposes such as www.hypercare.com | Operational | Component | Not recorded |
Notifications and Real-Time Syncing (Canadian Region) - Push notifications to mobile devices and web platform - Web sockets (real-time syncing and updates) - External notifications through SMS, Email, or Physical Pagers (numeric or alphanumeric) | Operational | Component | Not recorded |
Notifications and Real-Time Syncing (U.S. Region) - Push notifications to mobile devices and web platform - Web sockets (real-time syncing and updates) - External notifications through SMS, Email, or Physical Pagers (numeric or alphanumeric) | Operational | Component | Not recorded |
File Attachments (Canadian Region) - Images - Videos - Audio - Microsoft and PDF formats | Operational | Component | Not recorded |
File Attachments (U.S. Region) - Images - Videos - Audio - Microsoft and PDF formats | Operational | Component | Not recorded |
Payment Portal Responsible for payment processing | Operational | Component | Not recorded |
Viewing Who is On-Call (Canadian Region) - Finding out who is on-call by site and departments - Favouriting roles | Operational | Component | Not recorded |
Viewing Who is On-Call (U.S. Region) - Finding out who is on-call by site and departments - Favouriting roles | Operational | Component | Not recorded |
Code Teams (Canadian Region) - Activation of Code Teams (based on roles and or static users) - Escalations with fall back mechanisms | Operational | Component | Not recorded |
Code Teams (U.S. Region) - Activation of Code Teams (based on roles and or static users) - Escalations with fall back mechanisms | Operational | Component | Not recorded |
Self-serve Scheduling (Canadian Region) - Swift swapping - Schedule marketplace - My schedule | Operational | Component | Not recorded |
Self-serve Scheduling (U.S. Region) - Swift swapping - Schedule marketplace - My schedule | Operational | Component | Not recorded |
Administration and Scheduling (Canadian Region) - Managing users' profile information - Removing and adding users - Log out of users - Inputting and updating of schedules - Analytics | Operational | Component | Not recorded |
Administration and Scheduling (U.S. Region) - Managing users' profile information - Removing and adding users - Log out of users - Inputting and updating of schedules - Analytics | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Hypercare is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
4.76%
Known uptime
21 known history days
28
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
22
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
API & Integrations (Canadian Region)
Operational
API & Integrations (U.S. Region)
Operational
Administration and Scheduling (Canadian Region)
Operational
Administration and Scheduling (U.S. Region)
Operational
App Store Availability
Operational
1
operational days
0
degraded days
8
outage days
12
maintenance days
69
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Our engineering team has restored the service. Post mortem will be posted once it is available.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Scheduled maintenance completed. No downtime observed.
Scheduled maintenance is still in progress. We will provide updates as necessary.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Maintenance Status: Completed Completion Time: 4:20 AM ET The scheduled maintenance is now complete. While the window was extended to 4:30 AM ET to prioritize system stability during complex migrations, we are pleased to report that total downtime was kept under 60 seconds, strictly following our initial forecast. Impact Mitigation: By completing these activities tonight, Hypercare has fully neutralized any potential impact from our cloud providerâs (OCI) upcoming maintenance windows on: May 2nd (03:23 â 07:23 ET) May 6th (18:28 â 22:28 ET) The team remained online until 4:30 AM to conduct rigorous testing and monitoring. All systems are confirmed stable.
This is to recap the maintenance that went out on April 27th between the times from 00:01 to 1:45 ET. We had to extend the maintenance period from 00:30 to 1:45 am to ensure all system migrations are handled with maximum stability. During this window, less than 60 seconds of downtime was experienced which was the forecasted period of time. The team ran through additional tests and monitoring until 2:10 am to ensure the system was stable. As a result of this, there will no longer be a planned maintenance period on April 27th from 17:52 - 21:52.
Uptimus tracks the official Hypercare status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.hypercare.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
