TecAlliance TecDoc Outage History

TecAlliance TecDoc had 4 outages in the last 2 years totaling 6h 50m of downtime — averaging 0.2 incidents per month.

There were 4 TecAlliance TecDoc outages since July 22, 2024 totaling 6h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status-tecdoc.tecalliance.net

Critical May 28, 2025

TecDoc Web Service Region Specific Requests send to US-West-2 has an alert

Detected by Pingoru: May 28, 2025, 06:11 PM UTC
Resolved: May 28, 2025, 06:14 PM UTC
Duration: 3m

Affected: US-West-2Region AWS US-West-2

Timeline · 2 updates

investigating May 28, 2025, 06:11 PM UTC

HTTP Server Error 503 Service Unavailable The engineering team is investigating an issue with our TecDoc Web Service. During this time, users may experience some latency issues when accessing their regionally specific requests sent through the US-West-2 region. We apologize for the inconvenience and will share any updates once we have more information. Thank you for your patience. Time (UTC) : 2025-05-28T18:06:15
resolved May 28, 2025, 06:14 PM UTC

This incident has been resolved.

Read the full incident report →

Notice May 28, 2025

Webservices-getArticles

Detected by Pingoru: May 28, 2025, 05:42 PM UTC
Resolved: May 28, 2025, 05:47 PM UTC
Duration: 4m

Timeline · 2 updates

investigating May 28, 2025, 05:42 PM UTC

HTTP Server Error 503 Service Unavailable The engineering team is investigating an issue with our TecDoc Web Service. During this time, users may experience some latency issues. We apologize for the inconvenience and will share any updates once we have more information. Thank you for your patience. Time (UTC) : 2025-05-28T17:37:20
resolved May 28, 2025, 05:47 PM UTC

This incident has been resolved.

Read the full incident report →

Notice October 10, 2024

[Pingdom] webservice.tecalliance.services Pegasus-getLinkageTargets has an alert

Detected by Pingoru: Oct 10, 2024, 06:35 AM UTC
Resolved: Oct 10, 2024, 06:39 AM UTC
Duration: 4m

Timeline · 2 updates

investigating Oct 10, 2024, 06:35 AM UTC

Socket timeout, unable to connect to server The engineering team is investigating an issue with our TecDoc Web Service. During this time, users may experience some latency issues. We apologize for the inconvenience and will share any updates once we have more information. Thank you for your patience. Time (UTC) : 2024-10-10T06:29:45
resolved Oct 10, 2024, 06:39 AM UTC

This incident has been resolved.

Read the full incident report →

Major July 22, 2024

Catalogue Platform - "DBTaskRunner - Queue is full"

Detected by Pingoru: Jul 22, 2024, 08:02 AM UTC
Resolved: Jul 22, 2024, 02:41 PM UTC
Duration: 6h 38m

Affected: TecDoc CatalogueTecDoc White-Label SolutionsTecDoc Catalogue Admin ToolTecRMI OnlineOpticat Online

Timeline · 4 updates

investigating Jul 22, 2024, 08:02 AM UTC

The engineering team is investigating an issue with our TecDoc Catalogue. During this time, users may experience some issues when accessing. We apologize for the inconvenience and will share any updates once we have more information. Thank you for your patience.
identified Jul 22, 2024, 09:02 AM UTC

Our team made progress investigating the issue with the Catalogue Platform. We appreciate your patience and understanding during this time. - We found the issue. - We are applying a fix for the issue. We apologize for the inconvenience and will share any further updates once the fix is implemented. Thank you for your continued patience.
monitoring Jul 22, 2024, 10:34 AM UTC

Our team has made significant progress in resolving the issue with the Catalogue Platform. We appreciate your patience and understanding throughout this process. - The issue has been identified and fixed. - Systems are now operational, and we are monitoring the situation to ensure stability. We apologize for the inconvenience and will provide further updates if needed.
resolved Jul 22, 2024, 02:41 PM UTC

Our team has completely resolved the problem with the Catalogue Platform. We appreciate your patience and support during this time. - The root cause of the issue was identified and addressed. - All systems are functioning normally and are stable. We apologize for any disruption this may have caused.

Read the full incident report →