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
99.96 % 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
Apr 20, 2025

No incidents reported today.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025
Timeouts and Instability
Postmortem - Read details
Apr 15, 14:47 EDT
Resolved - On April 15, 2025, our application experienced Redis timeout errors, resulting in service degradation for approximately 3 hours. The root cause was thread pool exhaustion in the application server, triggered by a code change deployed on April 7, 2025. Post-mortem to follow.
Apr 15, 14:45 EDT
Update - The investigating continues, but we believe we've isolated the issue to the connection to the caching service. We've deployed a new instance of the caching server to try and alleviate that issue.
Apr 15, 13:36 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 15, 13:12 EDT
Investigating - We are currently investigating this issue.
Apr 15, 12:33 EDT
Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

Apr 11, 2025

No incidents reported.

Apr 10, 2025

No incidents reported.

Apr 9, 2025

No incidents reported.

Apr 8, 2025

No incidents reported.

Apr 7, 2025

No incidents reported.

Apr 6, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage