TidyHQ Outage History

TidyHQ is up right now

Pingoru has recorded 9 incidents for TidyHQ: 2 in the last 12 months and 2 in the last 90 days.

Source: status.tidyhq.com

9incidents recorded
2last 12 months
2last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct39%
Pingoru began tracking TidyHQ 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 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 20262197 of 510 (39%)

Incidents, newest first

Major October 12, 2026 Meetings & Minutes 2h 50m

Started Oct 12, 2026, 11:41 PM UTC· resolved Oct 13, 2026, 02:32 AM UTC

  1. investigating Oct 12, 2026, 11:41 PM UTC

    Editing meetings and minutes is currently unavailable. Sorry about that! We'll get it fixed as fast as we can.

  2. identified Oct 13, 2026, 01:01 AM UTC

    We've confirmed there is a problem, we're working to resolve it.

  3. resolved Oct 13, 2026, 02:32 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major October 4, 2025 Email queuing-related issue 12h 48m

Started Oct 04, 2025, 02:00 AM UTC· resolved Oct 04, 2025, 02:48 PM UTC

  1. resolved Oct 04, 2025, 02:48 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major August 24, 2025 Email rejections - Hotmail, Outlook & Live.com 22d 10h

Started Aug 24, 2025, 02:00 PM UTC· resolved Sep 16, 2025, 12:12 AM UTC

  1. resolved Sep 16, 2025, 12:12 AM UTC

    We've been informed that this is now fully resolved.

Read the full incident report →

Major June 16, 2025 Email queuing delays. 3d 16h

Started Jun 16, 2025, 07:00 AM UTC· resolved Jun 19, 2025, 11:43 PM UTC

  1. resolved Jun 26, 2025, 11:43 PM UTC

    We identified database performance as a cause of this issue last week. To improve it we’ve both upgraded the database CPU and RAM, and made some other configuration tweaks. It looks like there haven't been notable queuing issues since then.

Read the full incident report →