Togetherwork Outage History

Togetherwork is up right now

Pingoru has recorded 51 incidents for Togetherwork: 12 in the last 12 months and 3 in the last 90 days.

Source: status.togetherwork.com

51incidents recorded
12last 12 months
3last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov6%
Pingoru began tracking Togetherwork in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026111 of 720 (1%)
May 202626 of 744 (1%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202613 of 744 (0%)
September 202600 of 720 (0%)
October 2026120 of 744 (3%)
November 202619 of 142 (6%)

Incidents, newest first

Minor April 10, 2025 [SEV-3] Settlement File Delay 3h 48m File Import Process - Internal, File Import Process - External

Started Apr 10, 2025, 12:36 PM UTC· resolved Apr 10, 2025, 04:24 PM UTC

  1. investigating Apr 10, 2025, 12:36 PM UTC

    Regular settlement files and merchant settlement files will not be available by 9:00 a.m. eastern this morning. We will send an update as soon as we have more information and when the files are available.

  2. resolved Apr 10, 2025, 04:24 PM UTC

    All regular settlement files and merchant settlement files are now available. This incident is resolved.

Read the full incident report →

Minor April 3, 2025 [SEV-3] Settlement File Delay 2h 14m File Import Process - Internal, File Import Process - External

Started Apr 03, 2025, 12:50 PM UTC· resolved Apr 03, 2025, 03:04 PM UTC

  1. investigating Apr 03, 2025, 12:50 PM UTC

    Regular settlement files and merchant settlement files will not be available by 9:00 a.m. eastern this morning. We will send an update as soon as we have more information and when the files are available.

  2. resolved Apr 03, 2025, 03:04 PM UTC

    All regular settlement files and merchant settlement files are now available. This incident is resolved.

Read the full incident report →

Notice March 9, 2025 [SEV-3] Settlement/Comprehensive File Delay - 3/9/2025 1h 5m File Import Process - Internal, File Import Process - External

Started Mar 09, 2025, 12:55 PM UTC· resolved Mar 09, 2025, 02:00 PM UTC

  1. investigating Mar 09, 2025, 12:55 PM UTC

    Regular settlement files, comprehensive reports and merchant settlement files will not be available by 9:00 a.m. eastern this morning. We will send an update as soon as we have more information and when the files are available.

  2. resolved Mar 09, 2025, 02:00 PM UTC

    All regular settlement files, comprehensive reports and merchant settlement file are now available. This incident is resolved.

Read the full incident report →

Minor January 10, 2025 [SEV-3] Settlement/Comprehensive File Delay 46m File Import Process - Internal, File Import Process - External

Started Jan 10, 2025, 01:51 PM UTC· resolved Jan 10, 2025, 02:38 PM UTC

  1. investigating Jan 10, 2025, 01:51 PM UTC

    Regular settlement files, comprehensive reports and merchant settlement files will not be available by 9:00 a.m. eastern this morning. We will send an update as soon as we have more information and when the files are available.

  2. resolved Jan 10, 2025, 02:38 PM UTC

    All regular settlement files, comprehensive reports and merchant settlement file are now available. This incident is resolved.

Read the full incident report →

Notice December 10, 2024 [SEV-3] Settlement/Comprehensive File Delay 39m File Import Process - Internal, File Import Process - External

Started Dec 10, 2024, 01:49 PM UTC· resolved Dec 10, 2024, 02:29 PM UTC

  1. investigating Dec 10, 2024, 01:49 PM UTC

    Regular settlement files and merchant settlement files will not be available by 9:00 a.m. eastern this morning. We will send an update as soon as we have more information and when the files are available.

  2. resolved Dec 10, 2024, 02:29 PM UTC

    All regular settlement files and merchant settlement files are now available. This incident is resolved.

Read the full incident report →