TecAlliance TecDoc Outage History

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

There were 5 TecAlliance TecDoc outages since June 30, 2026 totaling 2h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Critical July 24, 2026

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

Detected by Pingoru: Jul 24, 2026, 11:06 AM UTC
Resolved: Jul 24, 2026, 11:36 AM UTC
Duration: 29m

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

Timeline · 2 updates

investigating Jul 24, 2026, 11:06 AM UTC

Network is unreachable 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) : 2026-07-24T11:01:15
resolved Jul 24, 2026, 11:36 AM UTC

This incident has been resolved.

Read the full incident report →

Critical June 30, 2026

TecDoc Web Service has an alert

Detected by Pingoru: Jun 30, 2026, 07:26 PM UTC
Resolved: Jun 30, 2026, 07:30 PM UTC
Duration: 4m

Affected: Aggregate all Regions

Timeline · 2 updates

investigating Jun 30, 2026, 07:26 PM UTC

The required string was not found 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) : 2026-06-30T19:21:42
resolved Jun 30, 2026, 07:30 PM UTC

This incident has been resolved.

Read the full incident report →

Notice June 30, 2026

Webservices-getArticles

Detected by Pingoru: Jun 30, 2026, 07:12 PM UTC
Resolved: Jun 30, 2026, 07:37 PM UTC
Duration: 24m

Timeline · 2 updates

investigating Jun 30, 2026, 07:12 PM UTC

The required string was not found 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) : 2026-06-30T19:07:20
resolved Jun 30, 2026, 07:37 PM UTC

This incident has been resolved.

Read the full incident report →

Notice June 30, 2026

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

Detected by Pingoru: Jun 30, 2026, 06:40 PM UTC
Resolved: Jun 30, 2026, 07:39 PM UTC
Duration: 59m

Timeline · 2 updates

investigating Jun 30, 2026, 06:40 PM 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) : 2026-06-30T18:34:45
resolved Jun 30, 2026, 07:39 PM UTC

This incident has been resolved.

Read the full incident report →

Critical June 30, 2026

TecDoc Web Service Region Specific Requests send to EU-Central-1 has an alert

Detected by Pingoru: Jun 30, 2026, 06:37 PM UTC
Resolved: Jun 30, 2026, 07:36 PM UTC
Duration: 58m

Affected: EU-Central-1Region AWS EU-Central-1

Timeline · 2 updates

investigating Jun 30, 2026, 06:37 PM 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 when accessing their regionally specific requests sent through the EU-Central-1 region. We apologize for the inconvenience and will share any updates once we have more information. Thank you for your patience. Time (UTC) : 2026-06-30T18:32:00
resolved Jun 30, 2026, 07:36 PM UTC

This incident has been resolved.

Read the full incident report →