kuraCloud Outage History

kuraCloud is up right now

Pingoru has recorded 48 incidents for kuraCloud: 3 in the last 12 months and 1 in the last 90 days.

Source: status.kuracloud.com

48incidents recorded
3last 12 months
1last 90 days
2 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking kuraCloud 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 2026116 of 744 (2%)
August 2026046 of 744 (6%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Minor July 31, 2026 Elevated error rate 2d 13h Global

Started Jul 31, 2026, 08:32 AM UTC· resolved Aug 02, 2026, 09:34 PM UTC

  1. investigating Jul 31, 2026, 08:32 AM UTC

    We are currently investigating an elevated error rate across LT and will update once we have identified the problem.

  2. identified Jul 31, 2026, 10:32 AM UTC

    The issue has been identified and a fix is being implemented but may take a few hours to restore normal functionality, this incident will be updated when the fix is complete.

  3. monitoring Jul 31, 2026, 02:10 PM UTC

    The fix has been implemented and normal performance should now be restored. We will continue to monitor the situation.

  4. resolved Aug 02, 2026, 09:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 4, 2025 Degraded performance in EU region 7h 34m Europe

Started Nov 04, 2025, 10:40 AM UTC· resolved Nov 04, 2025, 06:14 PM UTC

  1. identified Nov 04, 2025, 10:40 AM UTC

    The issue has been identified and a fix is being implemented, the service should return to normal shortly

  2. monitoring Nov 04, 2025, 10:49 AM UTC

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

  3. resolved Nov 04, 2025, 06:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 27, 2025 Elevated Error Rate 3d 13h Instance, Europe

Started Oct 27, 2025, 07:21 AM UTC· resolved Oct 30, 2025, 09:19 PM UTC

  1. investigating Oct 27, 2025, 07:21 AM UTC

    We are currently experiencing an elevated error rate and are investigating the issue.

  2. monitoring Oct 28, 2025, 12:29 AM UTC

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

  3. resolved Oct 30, 2025, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025 AWS Outage impacting our services 1d Accounts, Instance, North America

Started Oct 20, 2025, 09:31 AM UTC· resolved Oct 21, 2025, 10:27 AM UTC

  1. monitoring Oct 20, 2025, 09:31 AM UTC

    An Amazon Web Services outage has been impacting our services for the last 2 hours, including our ability to update this page. Now that AWS are seeing signs of recovery our services are returning to normal. We will continue to monitor the situation.

  2. resolved Oct 21, 2025, 10:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 2, 2025 Elevated API Errors 20m Accounts, Instance, Europe

Started Jun 02, 2025, 09:22 AM UTC· resolved Jun 02, 2025, 09:43 AM UTC

  1. monitoring Jun 02, 2025, 09:22 AM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. resolved Jun 02, 2025, 09:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 13, 2025 Degraded performance in North America 12d 3h North America

Started Mar 13, 2025, 09:10 PM UTC· resolved Mar 26, 2025, 01:09 AM UTC

  1. investigating Mar 13, 2025, 09:10 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 14, 2025, 03:05 AM UTC

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

  3. resolved Mar 26, 2025, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 13, 2025 Outage 49m Accounts, Global

Started Mar 13, 2025, 01:32 AM UTC· resolved Mar 13, 2025, 02:21 AM UTC

  1. investigating Mar 13, 2025, 01:32 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 13, 2025, 01:53 AM UTC

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

  3. resolved Mar 13, 2025, 02:21 AM UTC

    This incident has been resolved.

Read the full incident report →