Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

TigerConnect Outage History

Every past TigerConnect outage tracked by IsDown, with detection times, duration, and resolution details.

There were 66 TigerConnect outages since February 2015. The 9 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 22, 2026

May 2026: TigerConnect Platform Issue: TigerConnect Physician Scheduling - Investigating

Detected May 22, 2026 10:24 AM EDT · Resolved May 22, 2026 11:02 AM EDT · Duration 38 minutes

TigerConnect Physician Scheduling experienced a SAML authentication issue that prevented SSO users from logging in, causing them to get stuck in a continuous authentication loop after submitting credentials. The issue was detected at 7:00 AM PT and affected only users utilizing SAML-based single sign-on authentication. Engineers applied a fix at 7:50 AM PT and the incident was fully resolved by 7:51 AM PT, with the total outage lasting 38 minutes.

Minor May 6, 2026

May 2026: TigerConnect Platform Issue: Fast Deploys (emails) being triggered seemingly with no messages - Investigating

Detected May 6, 2026 9:25 AM EDT · Resolved May 6, 2026 10:18 AM EDT · Duration about 1 hour

TigerConnect experienced an issue with their email delivery service that caused multiple users to receive unwanted Fast Deploy emails without corresponding messages. The core messaging functionality remained unaffected during the 54-minute incident. The engineering team resolved the issue, which was related to a recent deployment.

Major April 22, 2026

April 2026: TigerConnect Platform Issue: Web/Desktop App Not loading - Investigating

Detected Apr 22, 2026 8:20 AM EDT · Resolved Apr 22, 2026 10:57 AM EDT · Duration about 3 hours

TigerConnect experienced a major platform issue lasting 2.6 hours where the desktop app and web sessions failed to load messages, and new logins remained stuck on loading screens without displaying conversations. The incident affected Directory Search and Messaging Services components, preventing users from accessing their conversations through web and desktop interfaces. The engineering team remediated the root cause and restored normal performance, with the incident fully resolved.