TecAlliance TecDoc Outage History

TecAlliance TecDoc is up right now

Pingoru has recorded 50 incidents for TecAlliance TecDoc: 11 in the last 12 months and 0 in the last 90 days.

Source: status-tecdoc.tecalliance.net

50incidents recorded
11last 12 months
0last 90 days
19 minutestypical duration
Incidents per month
0510JunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%JunJulAugSepOct0%
Pingoru began tracking TecAlliance TecDoc in June 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
June 2026101 of 720 (0%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 523 (0%)

Incidents, newest first

Critical July 24, 2026 TecDoc Web Service Region Specific Requests send to US-West-2 has an alert 29m US-West-2, Region AWS US-West-2

Started Jul 24, 2026, 11:06 AM UTC· resolved Jul 24, 2026, 11:36 AM UTC

  1. 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

  2. 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 4m Aggregate all Regions

Started Jun 30, 2026, 07:26 PM UTC· resolved Jun 30, 2026, 07:30 PM UTC

  1. 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

  2. resolved Jun 30, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 30, 2026 Webservices-getArticles 24m

Started Jun 30, 2026, 07:12 PM UTC· resolved Jun 30, 2026, 07:37 PM UTC

  1. 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

  2. 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 59m

Started Jun 30, 2026, 06:40 PM UTC· resolved Jun 30, 2026, 07:39 PM UTC

  1. 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

  2. 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 58m EU-Central-1, Region AWS EU-Central-1

Started Jun 30, 2026, 06:37 PM UTC· resolved Jun 30, 2026, 07:36 PM UTC

  1. 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

  2. resolved Jun 30, 2026, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →