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

Tekion Outage History

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

There were 65 Tekion outages since May 2025. The 65 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor February 28, 2026

February 2026: Retail Application - Deal Loading Slowness

Detected Feb 28, 2026 3:28 PM EST · Resolved Feb 28, 2026 6:10 PM EST · Duration about 3 hours

Tekion's Retail Application experienced slowness when loading the Deals list and individual deals, preventing dealers from proceeding with deal desking operations. The issue affected the Retail component for 2.7 hours while the team investigated and identified the root cause. The problem was resolved and all functionality returned to normal, with users advised to refresh their browsers if issues persisted.

Minor February 26, 2026

February 2026: CRM - Delays with Lead Assignment Triggers

Detected Feb 26, 2026 12:36 PM EST · Resolved Feb 26, 2026 1:58 PM EST · Duration about 1 hour

Tekion's CRM system experienced delays with Lead Assignment rules triggering, which prevented associated process automations from running automatically. The issue affected the CRM component for 1.4 hours, with users able to work around the problem by manually assigning leads to trigger the automation immediately. The engineering team identified and resolved the issue, restoring normal lead assignment and process automation functionality.

Minor February 24, 2026

February 2026: Tekion ARC CRM Application Issue - Tasks and Rules Engine

Detected Feb 24, 2026 11:11 AM EST · Resolved Feb 24, 2026 1:42 PM EST · Duration about 3 hours

The Tekion ARC CRM application experienced delays in task creation and Rule Engine processing for 2.5 hours. The CRM component was affected, causing processing delays for users trying to create tasks and utilize rule-based functionality. The issue was identified and resolved by the engineering team, who continued working on reprocessing the impacted leads and tasks after service restoration.