Jellyfish Outage History

Jellyfish is up right now

Pingoru has recorded 15 incidents for Jellyfish: 0 in the last 12 months and 0 in the last 90 days.

Source: status.jellyfish.co

15incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Jellyfish 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 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 523 (0%)

Incidents, newest first

Notice October 20, 2025 Widespread AWS Outage Affecting Jellyfish App 21h 39m Web Application, Data Ingestion

Started Oct 20, 2025, 01:56 PM UTC· resolved Oct 21, 2025, 11:35 AM UTC

  1. investigating Oct 20, 2025, 01:56 PM UTC

    Ongoing widespread AWS outage is affecting some Jellyfish services. The web app is currently unavailable and we are actively working to mitigate.

  2. identified Oct 20, 2025, 06:59 PM UTC

    AWS is rolling mitigations through us-east. The Jellyfish web app is back, though some underlying services like DFO report generation and data ingestion may still be affected. We are continuing to monitor the situation and will post updates here.

  3. monitoring Oct 21, 2025, 12:44 AM UTC

    The AWS Incident has been resolved, and Jellyfish infrastructure is operational. We are continuing to monitor some dependencies on other 3rd parties. Data processing is still delayed.

  4. monitoring Oct 21, 2025, 02:08 AM UTC

    All services are operational. We are continuing to monitor.

  5. resolved Oct 21, 2025, 11:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025 Web App Unavailable - Upstream AWS Failure –

Started Oct 20, 2025, 07:30 AM UTC· resolved Oct 20, 2025, 07:30 AM UTC

  1. resolved Oct 20, 2025, 01:45 PM UTC

    The Jellyfish web app is now back online after some unavailability.

Read the full incident report →

Major May 27, 2025 App Down 3h 33m Web Application

Started May 27, 2025, 01:12 PM UTC· resolved May 27, 2025, 04:46 PM UTC

  1. identified May 27, 2025, 01:55 PM UTC

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

  2. identified May 27, 2025, 01:57 PM UTC

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

  3. identified May 27, 2025, 02:03 PM UTC

    We've identified a fault in one of our third-party providers and are actively working towards a way to mitigate.

  4. monitoring May 27, 2025, 03:32 PM UTC

    Our third party service provider issue has been mitigated. We are currently monitoring our system to ensure our service's stability.

  5. monitoring May 27, 2025, 04:46 PM UTC

    After monitoring our systems for the past hour we've determined that the fix deployed by our vendor was successful and our web application has returned to normal operation.

  6. resolved May 27, 2025, 04:46 PM UTC

    This incident was successfully resolved at 11:46AM EST.

Read the full incident report →

Major March 19, 2025 App Unavailable 4h 35m Web Application

Started Mar 19, 2025, 02:49 PM UTC· resolved Mar 19, 2025, 07:24 PM UTC

  1. investigating Mar 19, 2025, 02:49 PM UTC

    Jellyfish is currently unavailable. We are actively investigating and will resolve as quickly as possible. We apologize for the inconvenience.

  2. monitoring Mar 19, 2025, 03:12 PM UTC

    Jellyfish is now available, we are continuing to monitor the situation.

  3. resolved Mar 19, 2025, 07:24 PM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Major November 21, 2024 App unavailable 40m Web Application

Started Nov 21, 2024, 05:13 PM UTC· resolved Nov 21, 2024, 05:53 PM UTC

  1. identified Nov 21, 2024, 07:37 PM UTC

    The Jellyfish web app may be unavailable for some users. We are investigating.

  2. resolved Nov 21, 2024, 07:37 PM UTC

    This incident has been resolved.

Read the full incident report →