ResDiary Outage History

ResDiary is up right now

ResDiary had 18 outages in the last 2 years totaling 167h 52m of downtime — averaging 0.7 incidents per month.

There were 18 ResDiary outages since June 25, 2025 totaling 167h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.resdiary.com

Major June 11, 2026

Access Identity down

Detected by Pingoru
Jun 11, 2026, 08:38 AM UTC
Resolved
Jun 11, 2026, 08:38 AM UTC
Duration
—
Affected: Login
Timeline · 5 updates
  1. investigating Jun 10, 2026, 10:31 AM UTC

    Access Group is aware of an issue affecting Identity and all associated services. Access technical engineers have identified the fault and are working - as a priority activity - to resolve this. Access is committed to the highest levels of service quality; we apologise for the disruption caused and will provide further updates as swiftly as possible.

  2. investigating Jun 10, 2026, 10:34 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 10, 2026, 12:25 PM UTC

    Access Group is aware of an issue that affected EVO & Identity and all associated services. Access technical engineers deployed some technical mitigations - as a priority activity - to resolve this. Access is committed to the highest levels of service quality; we apologise for the disruption caused and will provide further updates as swiftly as possible.

  4. monitoring Jun 10, 2026, 06:25 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 11, 2026, 08:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

Reserve With Google Not Showing Availability

Detected by Pingoru
Jun 02, 2026, 02:16 PM UTC
Resolved
Jun 04, 2026, 02:08 PM UTC
Duration
1d 23h
Affected: Reserve with Google
Timeline · 2 updates
  1. monitoring Jun 02, 2026, 02:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Jun 04, 2026, 02:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 1, 2026

Issue Loading Diary Bookings

Detected by Pingoru
Jun 01, 2026, 07:36 AM UTC
Resolved
Jun 01, 2026, 08:15 AM UTC
Duration
39m
Affected: UK/Europe
Timeline · 3 updates
  1. investigating Jun 01, 2026, 07:36 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 01, 2026, 07:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 01, 2026, 08:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 25, 2026

Resdiary - Login

Detected by Pingoru
May 25, 2026, 07:43 AM UTC
Resolved
May 25, 2026, 10:44 AM UTC
Duration
3h 1m
Affected: UK/EuropeLoginDishcult on AndroidAustraliaDishcult on iOSNorth Central USAPIResDiary Plus on AndroidS.E. ASIAWidgetResDiary Plus on iOSEast AsiaReserve with GoogleWidget ConfiguratorDishcult Portal
Timeline · 5 updates
  1. investigating May 25, 2026, 07:43 AM UTC

    We are currently investigating an issue regarding users logging into their accounts

  2. identified May 25, 2026, 08:49 AM UTC

    We have identified the issue, and we're beginning a fix.

  3. monitoring May 25, 2026, 09:51 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring May 25, 2026, 10:10 AM UTC

    The fix has now rolled out successfully. Early indications are that this has resolved the issue. We are continuing to monitor the situation.

  5. resolved May 25, 2026, 10:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026

Degraded performance on reports

Detected by Pingoru
May 13, 2026, 03:37 PM UTC
Resolved
May 13, 2026, 05:15 PM UTC
Duration
1h 38m
Affected: North Central US
Timeline · 2 updates
  1. investigating May 13, 2026, 03:37 PM UTC

    We are currently investigating this issue.

  2. resolved May 13, 2026, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Slow responses in reports

Detected by Pingoru
May 11, 2026, 12:37 PM UTC
Resolved
May 11, 2026, 02:45 PM UTC
Duration
2h 8m
Affected: UK/Europe
Timeline · 4 updates
  1. investigating May 11, 2026, 12:37 PM UTC

    We are currently investigating this issue.

  2. investigating May 11, 2026, 01:49 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 11, 2026, 02:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 11, 2026, 02:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 9, 2026

ase.resdiary.com unavailable

Detected by Pingoru
May 09, 2026, 11:43 AM UTC
Resolved
May 09, 2026, 11:50 AM UTC
Duration
7m
Affected: East Asia
Timeline · 4 updates
  1. investigating May 09, 2026, 11:43 AM UTC

    We are currently investigating the incident.

  2. identified May 09, 2026, 11:47 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 09, 2026, 11:49 AM UTC

    We are continuing to work on a fix for this issue.

  4. resolved May 09, 2026, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 21, 2026

Widget Down

Detected by Pingoru
Apr 21, 2026, 08:50 AM UTC
Resolved
Apr 21, 2026, 09:07 AM UTC
Duration
16m
Affected: Widget
Timeline · 3 updates
  1. investigating Apr 21, 2026, 08:50 AM UTC

    We are currently investigating this issue.

  2. identified Apr 21, 2026, 09:01 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 21, 2026, 09:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 4, 2026

EPOS API Outage

Detected by Pingoru
Mar 04, 2026, 10:38 AM UTC
Resolved
Mar 04, 2026, 11:00 AM UTC
Duration
22m
Affected: API
Timeline · 4 updates
  1. investigating Mar 04, 2026, 10:38 AM UTC

    We are currently investigating this issue.

  2. identified Mar 04, 2026, 10:39 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 04, 2026, 10:41 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 04, 2026, 11:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 24, 2026

Epos API Slowness

Detected by Pingoru
Jan 24, 2026, 05:24 PM UTC
Resolved
Jan 24, 2026, 06:36 PM UTC
Duration
1h 12m
Affected: API
Timeline · 2 updates
  1. investigating Jan 24, 2026, 05:24 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 24, 2026, 06:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2025

Resdiary services down due to Cloudflare outage

Detected by Pingoru
Dec 05, 2025, 09:13 AM UTC
Resolved
Dec 05, 2025, 09:13 AM UTC
Duration
—
Affected: Login
Timeline · 1 update
  1. resolved Dec 05, 2025, 09:13 AM UTC

    ResDiary services experienced downtime due to a widespread Cloudflare outage impacting network connectivity and availability.

Read the full incident report →

Critical December 5, 2025

ResDiary Unavailable

Detected by Pingoru
Dec 05, 2025, 09:12 AM UTC
Resolved
Dec 05, 2025, 12:21 PM UTC
Duration
3h 8m
Affected: LoginDishcult Portal
Timeline · 4 updates
  1. investigating Dec 05, 2025, 09:12 AM UTC

    We are experiencing an issue with one of our third party software providers. This is affecting Access Identity logins and Dishcult.

  2. monitoring Dec 05, 2025, 09:19 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Dec 05, 2025, 12:21 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 05, 2025, 12:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 2, 2025

Elevated CPU Usage on Australia Diary Service

Detected by Pingoru
Dec 02, 2025, 05:58 AM UTC
Resolved
Dec 02, 2025, 06:27 AM UTC
Duration
29m
Affected: Australia
Timeline · 2 updates
  1. investigating Dec 02, 2025, 05:58 AM UTC

    We are currently investigating elevated CPU utilization on the Australia Diary production environment. This may result in degraded performance for some users. Our engineering team is actively working to identify the root cause and implement a resolution. Impact: Users may experience slower response times or intermittent issues when accessing the Australia Diary service.

  2. resolved Dec 02, 2025, 06:27 AM UTC

    The issue has been resolved by increasing the resource allocation.

Read the full incident report →

Critical December 1, 2025

Login unavailable

Detected by Pingoru
Dec 01, 2025, 09:29 AM UTC
Resolved
Dec 01, 2025, 01:27 PM UTC
Duration
3h 57m
Affected: Login
Timeline · 4 updates
  1. investigating Dec 01, 2025, 09:29 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 01, 2025, 09:35 AM UTC

    Access Group is aware of an issue affecting Access Identity which is impacting multiple products. Access technical engineers have identified the fault and are working - as a priority activity - to resolve this. Access is committed to the highest levels of service quality; we apologise for the disruption caused and will provide further updates as swiftly as possible

  3. monitoring Dec 01, 2025, 11:20 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 01, 2025, 01:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 21, 2025

Slowness in Login service

Detected by Pingoru
Nov 21, 2025, 10:52 AM UTC
Resolved
Nov 21, 2025, 11:48 AM UTC
Duration
55m
Affected: Login
Timeline · 5 updates
  1. investigating Nov 21, 2025, 10:52 AM UTC

    We are investigating some slowness in our Login service

  2. monitoring Nov 21, 2025, 10:59 AM UTC

    We have implemented a fix and are monitoring the outcome.

  3. identified Nov 21, 2025, 11:14 AM UTC

    We have identified a fix and are waiting for it to go out

  4. monitoring Nov 21, 2025, 11:28 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 21, 2025, 11:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 15, 2025

Reserve with Google incident

Detected by Pingoru
Nov 15, 2025, 02:09 PM UTC
Resolved
Nov 19, 2025, 02:19 PM UTC
Duration
4d
Affected: Reserve with Google
Timeline · 5 updates
  1. investigating Nov 15, 2025, 02:09 PM UTC

    We are currently investigating an issue with Reserve with Google

  2. identified Nov 15, 2025, 02:31 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Nov 15, 2025, 02:51 PM UTC

    We have identified an issue that caused our Reserve with Google integration to be disabled. The underlying issue has been resolved, but we've been unable to re-enable the Reserve with Google integration. We are continuing to work on this.

  4. identified Nov 17, 2025, 10:35 AM UTC

    We are continuing to work on re-enabling our Reserve with Google integration. We have identified that customers are still able to update existing bookings, they just can't create new ones.

  5. resolved Nov 19, 2025, 02:19 PM UTC

    This incident has been resolved

Read the full incident report →

Minor November 13, 2025

Login Degraded Performance

Detected by Pingoru
Nov 13, 2025, 11:01 AM UTC
Resolved
Nov 13, 2025, 04:35 PM UTC
Duration
5h 33m
Affected: Login
Timeline · 4 updates
  1. investigating Nov 13, 2025, 11:01 AM UTC

    We are aware of slowness while logging in. We are currently investigating this issue.

  2. monitoring Nov 13, 2025, 11:40 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Nov 13, 2025, 01:19 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 13, 2025, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 25, 2025

Diary Outage

Detected by Pingoru
Jun 25, 2025, 01:48 PM UTC
Resolved
Jun 25, 2025, 02:05 PM UTC
Duration
16m
Affected: UK/EuropeAustraliaNorth Central USAPIS.E. ASIAWidgetEast AsiaReserve with Google
Timeline · 7 updates
  1. investigating Jun 25, 2025, 01:48 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 25, 2025, 01:53 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 25, 2025, 01:56 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jun 25, 2025, 02:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Jun 25, 2025, 02:01 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Jun 25, 2025, 02:04 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 25, 2025, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →