Juro Outage History

Juro is up right now

Juro had 5 outages in the last 2 years totaling 16h 30m of downtime, averaging 0.2 incidents per month.

There were 5 Juro outages since March 23, 2026 totaling 16h 30m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.juro.com

Minor July 30, 2026

Application instance restarts

Detected by Pingoru
Jul 30, 2026, 09:40 AM UTC
Resolved
Jul 30, 2026, 12:25 PM UTC
Duration
2h 44m
Timeline · 4 updates
  1. investigating Jul 30, 2026, 09:40 AM UTC

    .

  2. identified Jul 30, 2026, 10:50 AM UTC

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

  3. monitoring Jul 30, 2026, 12:06 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Jul 30, 2026, 12:25 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor June 22, 2026

The application is slow to respond.

Detected by Pingoru
Jun 22, 2026, 07:10 AM UTC
Resolved
Jun 22, 2026, 10:06 AM UTC
Duration
2h 56m
Timeline · 2 updates
  1. identified Jun 22, 2026, 07:10 AM UTC

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

  2. resolved Jun 22, 2026, 10:06 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor April 13, 2026

DOCX Processing Issues

Detected by Pingoru
Apr 13, 2026, 08:51 PM UTC
Resolved
Apr 14, 2026, 07:00 AM UTC
Duration
10h 9m
Timeline · 4 updates
  1. investigating Apr 13, 2026, 08:51 PM UTC

    We are currently investigating this incident..

  2. identified Apr 14, 2026, 06:37 AM UTC

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

  3. monitoring Apr 14, 2026, 06:47 AM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Apr 14, 2026, 07:00 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 23, 2026

Latency issues with the main app

Detected by Pingoru
Mar 23, 2026, 01:18 PM UTC
Resolved
Mar 23, 2026, 01:58 PM UTC
Duration
40m
Timeline · 4 updates
  1. investigating Mar 23, 2026, 01:18 PM UTC

    We are currently investigating this incident..

  2. identified Mar 23, 2026, 01:22 PM UTC

    The issue has been identified. We're working towards a fix..

  3. monitoring Mar 23, 2026, 01:44 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Mar 23, 2026, 01:58 PM UTC

    This incident has been resolved..

Read the full incident report →