Notice history - Juro Status

~0.0 ms

99.99% uptime

Feb 2026 · 100.0%Mar · 99.98%Apr · 100.0%

Feb 2026

Mar 2026

Apr 2026

100.0% uptime

Feb 2026 · 100.0%Mar · 100.0%Apr · 100.0%

Feb 2026

Mar 2026

Apr 2026

100.0% uptime

Feb 2026 · 100.0%Mar · 100.0%Apr · 100.0%

Feb 2026

Mar 2026

Apr 2026

99.05% uptime

Feb 2026 · 100.0%Mar · 98.63%Apr · 98.62%

Feb 2026

Mar 2026

Apr 2026

Notice history

View current status

Apr 2026

Resolved
April 14, 2026 at 07 00UTC
Resolved
April 14, 2026 at 07 00UTC
This incident has been resolved.
Monitoring
April 14, 2026 at 06 47UTC
Monitoring
April 14, 2026 at 06 47UTC
We implemented a fix and are currently monitoring the result.
Identified
April 14, 2026 at 06 37UTC
Identified
April 14, 2026 at 06 37UTC
We are continuing to work on a fix for this incident.
Investigating
April 13, 2026 at 20 51UTC
Investigating
April 13, 2026 at 20 51UTC
We are currently investigating this incident.

Mar 2026

Resolved
March 24, 2026 at 09 23UTC
Resolved
March 24, 2026 at 09 23UTC
This incident has been resolved.
Investigating
March 23, 2026 at 23 11UTC
Investigating
March 23, 2026 at 23 11UTC
We are currently investigating this incident.

Resolved
March 23, 2026 at 13 58UTC
Resolved
March 23, 2026 at 13 58UTC
This incident has been resolved.
Monitoring
March 23, 2026 at 13 44UTC
Monitoring
March 23, 2026 at 13 44UTC
We implemented a fix and are currently monitoring the result.
Identified
March 23, 2026 at 13 22UTC
Identified
March 23, 2026 at 13 22UTC
The issue has been identified. We're working towards a fix.
Investigating
March 23, 2026 at 13 18UTC
Investigating
March 23, 2026 at 13 18UTC
We are currently investigating this incident.

Feb 2026

No notices reported this month

Feb 2026 to Apr 2026