Resly Outage History

Resly is up right now

Pingoru has recorded 32 incidents for Resly: 16 in the last 12 months and 3 in the last 90 days.

Source: resly.statuspage.io

32incidents recorded
16last 12 months
3last 90 days
6 daystypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct15%
Pingoru began tracking Resly 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 2026491 of 720 (13%)
May 20261261 of 744 (35%)
June 2026294 of 720 (13%)
July 2026146 of 744 (6%)
August 20262122 of 744 (16%)
September 202600 of 720 (0%)
October 2026188 of 589 (15%)

Incidents, newest first

Notice January 9, 2025 Test 2 4m

Started Jan 09, 2025, 09:20 PM UTC· resolved Jan 09, 2025, 09:25 PM UTC

  1. identified Jan 09, 2025, 09:20 PM UTC

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

  2. resolved Jan 09, 2025, 09:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 9, 2025 Test incident 3m

Started Jan 09, 2025, 09:15 PM UTC· resolved Jan 09, 2025, 09:19 PM UTC

  1. monitoring Jan 09, 2025, 09:15 PM UTC

    We are monitoring the situation and will update when we here more

  2. resolved Jan 09, 2025, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 9, 2025 Test incident - please ignore 14m

Started Jan 09, 2025, 08:49 PM UTC· resolved Jan 09, 2025, 09:03 PM UTC

  1. investigating Jan 09, 2025, 08:49 PM UTC

    We are currently investigating this issue.

  2. identified Jan 09, 2025, 08:56 PM UTC

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

  3. resolved Jan 09, 2025, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 7, 2025 Test Incident 2 - With component connected 5m

Started Jan 07, 2025, 10:49 PM UTC· resolved Jan 07, 2025, 10:54 PM UTC

  1. investigating Jan 07, 2025, 10:49 PM UTC

    This is just a test! We are checking on the incident process works when connected to a component

  2. identified Jan 07, 2025, 10:49 PM UTC

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

  3. monitoring Jan 07, 2025, 10:50 PM UTC

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

  4. monitoring Jan 07, 2025, 10:51 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 07, 2025, 10:54 PM UTC

    This test incident has been resolved

Read the full incident report →

Notice January 7, 2025 Test Incident - not connected to any component 5m

Started Jan 07, 2025, 10:48 PM UTC· resolved Jan 07, 2025, 10:54 PM UTC

  1. investigating Jan 07, 2025, 10:48 PM UTC

    Please note this is just a test ! Here is a description of said incident.

  2. resolved Jan 07, 2025, 10:54 PM UTC

    This incident has been resolved.

Read the full incident report →