Juro Outage History

Juro is up right now

Juro had 3 outages in the last 2 years totaling 1h 55m of downtime — averaging 0.1 incidents per month.

There were 3 Juro outages since March 23, 2026 totaling 1h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.juro.com

Minor June 17, 2026

Increased application error rate

Detected by Pingoru
Jun 17, 2026, 07:55 AM UTC
Resolved
Jun 17, 2026, 09:50 AM UTC
Duration
1h 55m
Affected: Core Services
Timeline · 3 updates
  1. identified Jun 17, 2026, 09:35 AM UTC

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

  2. monitoring Jun 17, 2026, 09:48 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 17, 2026, 09:50 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 13, 2026, 08:51 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 13, 2026, 08:51 PM UTC

    Type: Incident Duration: 10 hours and 9 minutes Affected Components: Document Services Apr 13, 20:51:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 14, 06:37:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 14, 06:47:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 14, 07:00:00 GMT+0 - Resolved - 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:18 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 23, 2026, 01:18 PM UTC

    Type: Incident Duration: 40 minutes Affected Components: Core Services Mar 23, 13:18:18 GMT+0 - Investigating - We are currently investigating this incident. Mar 23, 13:22:48 GMT+0 - Identified - The issue has been identified. We're working towards a fix. Mar 23, 13:44:35 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 23, 13:58:35 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →