All Systems Operational

About This Site

We continuously monitor the status of CabMD and all its related services. If there are any interruptions in service, a note will be posted here. If you are experiencing problems connecting to CabMD and do not see a notice posted, please email support@cab.md.

Uptime over the past 90 days. View historical uptime.
Website Frontend (http://www.cab.md) ? Operational
90 days ago
100.0 % uptime
Today
Website Backend (https://my.cab.md) ? Operational
API (api.cab.md) ? Operational
MOHLTC's MCEDT Service ? Operational
90 days ago
100.0 % uptime
Today
MOHLTC's HCV Service ? Operational
90 days ago
100.0 % uptime
Today
DNSimple Name Servers Operational
Chargify API Operational
Chargify Scheduled Payment Processing Operational
Chargify Main Application Operational
Intercom Intercom message delivery Operational
Intercom Intercom Webhooks Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
Landing Site Uptime (www.cab.md)
Fetching
Jul 18, 2025

No incidents reported today.

Jul 17, 2025

No incidents reported.

Jul 16, 2025

No incidents reported.

Jul 15, 2025
API Service Down
Resolved - Incident Summary
Date: July 15, 2025
Time: 4:42 am
Severity: High
Duration: ~ 5 hours
Status: Resolved

Issue Description
The CabMD API experienced a critical failure due to a missing SQL Server Native Client library dependency. The application was unable to load the required DLL file `Microsoft.Data.SqlClient.SNI.x64.dll`, resulting in a complete service outage.

Impact
- Complete unavailability of the CabMD API
- Mobile application non-functional

Root Cause
Suspected Cause: Azure infrastructure-related issue
Evidence:
- Issue occurred during off-hours with no recent deployments or changes
- Missing system library suggests infrastructure-level disruption
- Timing aligns with potential Azure maintenance or updates

Investigation Status: Root cause analysis ongoing

Resolution
1. Immediate Action: Restored the missing Microsoft.Data.SqlClient.SNI.x64.dll library
2. Deployment: Redeployed the application with the restored dependency
3. Verification: Confirmed system functionality and database connectivity restored

Timeline
- 7 AM - Issue detected
- 9:30 AM - Investigation began
- 9:31 AM - Missing library identified
- 9:34 AM - Library restored and redeployment initiated
- 9:35 AM - Service fully restored

Follow-up Actions
1. Monitoring: Enhanced monitoring for dependency-related failures
2. Infrastructure Review: Coordinate with Azure support to investigate potential infrastructure issues
3. Preventive Measures:
- Review deployment artifacts to ensure all dependencies are properly packaged
- Consider implementing dependency health checks
- Document recovery procedures for similar incidents
Jul 15, 04:30 EDT
Jul 14, 2025

No incidents reported.

Jul 13, 2025

No incidents reported.

Jul 12, 2025

No incidents reported.

Jul 11, 2025

No incidents reported.

Jul 10, 2025

No incidents reported.

Jul 9, 2025

No incidents reported.

Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage