New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Services Pricing Dashboard

Connecteam Outage History

Uptime record, past incidents, and downtime history for Connecteam.

Checking current status...
94.5% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Mar 30Jun 27

Monthly Uptime

Month Uptime Days Tracked Days with Issues
June 2026 92.6% 27 2
May 2026 90.3% 31 3
April 2026 100% 30 0
March 2026 100% 3 0

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Mar 29 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

June 2026
Degraded Performance in Schedule
minor

Started: Jun 15, 4:15 PM

monitoring
A fix has been implemented and we are monitoring the results.
Jun 15, 5:05 PM
identified
The issue has been identified and a fix is being implemented.
Jun 15, 4:33 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 15, 4:26 PM
investigating
We are currently investigating this issue.
Jun 15, 4:15 PM
Degraded performance in Time Clock and Time Off
minor

Started: Jun 1, 2:26 PM

identified
The issue has been identified and a fix is being implemented.
Jun 1, 2:30 PM
investigating
We are currently investigating this issue.
Jun 1, 2:26 PM
May 2026
Major Outage
critical

Started: May 18, 10:06 AM

monitoring
A fix has been implemented and we are monitoring the results.
May 18, 10:16 AM
identified
The issue has been identified and a fix is being implemented.
May 18, 10:12 AM
investigating
We are currently investigating this issue.
May 18, 10:06 AM
Major Outage
critical

Started: May 15, 5:48 AM

monitoring
A fix has been implemented and we are monitoring the results.
May 15, 6:02 AM
identified
The issue has been identified and a fix is being implemented.
May 15, 5:55 AM
investigating
We are currently investigating this issue.
May 15, 5:48 AM
Major Outage
critical

Started: May 13, 2:27 PM

monitoring
A fix has been implemented and we are monitoring the results.
May 13, 2:50 PM
identified
We have identified the issue and are working on a fix
May 13, 2:28 PM
identified
We are currently investigating this issue.
May 13, 2:27 PM