Tekion incident

Azure Service Outage Impacting 3rd-Party Integrations

Minor Resolved View vendor source →

Tekion experienced a minor incident on October 29, 2025 affecting Accounting and Parts and 1 more component, lasting 6h 22m. The incident has been resolved; the full update timeline is below.

Started
Oct 29, 2025, 04:55 PM UTC
Resolved
Oct 29, 2025, 11:18 PM UTC
Duration
6h 22m
Detected by Pingoru
Oct 29, 2025, 04:55 PM UTC

Affected components

AccountingPartsRetailServiceCoreAnalyticsCRMPayrollIntegrations

Update timeline

  1. monitoring Oct 29, 2025, 04:55 PM UTC

    We are aware of an active service outage reported by Microsoft Azure. While Tekion ARC is hosted on AWS and remains fully operational, some of our integrated 3rd-party partners—such as RouteOne—may currently experience degraded performance or intermittent connectivity as a result of the Azure disruption. We are actively monitoring the situation and will provide updates as more information becomes available. Thank you for your patience and understanding.

  2. monitoring Oct 29, 2025, 11:14 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Oct 29, 2025, 11:18 PM UTC

    The recent Microsoft Azure service disruption has been resolved. Tekion’s core platform, hosted on AWS, remained fully operational throughout the event, and your critical business functions continued without interruption. As with most technology providers, some Tekion integrations rely on third-party partners who may themselves use cloud services like Azure. In these cases, a few integrations—such as RouteOne—may have experienced intermittent connectivity or delays. These services have now been restored and are operating normally. Tekion’s cloud-native architecture is designed for resilience and business continuity, with multiple safeguards and fallback workflows in place to minimize exposure to third-party outages. If you have any questions or continue to experience anomalies, please reach out to our Support team.

  4. resolved Oct 29, 2025, 11:18 PM UTC

    This incident has been resolved.