Quartzy Outage History

Quartzy is up right now

Quartzy had 5 outages in the last 2 years totaling 5h 4m of downtime — averaging 0.2 incidents per month.

There were 5 Quartzy outages since August 12, 2024 totaling 5h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.quartzy.com

Minor January 7, 2026

Service Degradation

Detected by Pingoru
Jan 07, 2026, 08:09 PM UTC
Resolved
Jan 07, 2026, 08:14 PM UTC
Duration
4m
Affected: Quartzy Web ApplicationQuartzy Mobile ApplicationQuartzy Integrations
Timeline · 3 updates
  1. investigating Jan 07, 2026, 08:09 PM UTC

    Currently impacting order request flows.

  2. monitoring Jan 07, 2026, 08:11 PM UTC

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

  3. resolved Jan 07, 2026, 08:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 29, 2025

Service Disruption - Application Unavailable

Detected by Pingoru
Dec 29, 2025, 11:20 PM UTC
Resolved
Dec 30, 2025, 01:22 AM UTC
Duration
2h 2m
Affected: Quartzy Web ApplicationQuartzy Mobile ApplicationQuartzy Integrations
Timeline · 5 updates
  1. investigating Dec 29, 2025, 11:20 PM UTC

    We are currently experiencing a service disruption where the application is not loading for users. Our engineering team is actively investigating the issue and working to restore service as quickly as possible. We will provide updates as more information becomes available.

  2. identified Dec 29, 2025, 11:42 PM UTC

    We've identified the issue and are working on a fix.

  3. identified Dec 30, 2025, 12:27 AM UTC

    We are continuing our efforts to get this resolve as soon as possible.

  4. monitoring Dec 30, 2025, 01:15 AM UTC

    A fix has been deployed and things are starting to come back up, degraded performance expected temporarily as things get moving again. We're monitoring to ensure full stability.

  5. resolved Dec 30, 2025, 01:22 AM UTC

    Services appear to be stable. We will continue to monitor.

Read the full incident report →

Major June 30, 2025

Service Disruption

Detected by Pingoru
Jun 30, 2025, 12:50 PM UTC
Resolved
Jun 30, 2025, 02:55 PM UTC
Duration
2h 4m
Affected: Quartzy Web ApplicationQuartzy Mobile ApplicationQuartzy Integrations
Timeline · 7 updates
  1. investigating Jun 30, 2025, 12:50 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 30, 2025, 12:50 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 30, 2025, 01:11 PM UTC

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

  4. monitoring Jun 30, 2025, 01:20 PM UTC

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

  5. monitoring Jun 30, 2025, 01:31 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Jun 30, 2025, 02:00 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 30, 2025, 02:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2024

Deliveries to Northern California may be Delayed

Detected by Pingoru
Dec 05, 2024, 08:06 PM UTC
Resolved
Dec 05, 2024, 08:16 PM UTC
Duration
10m
Affected: Quartzy Web Application
Timeline · 2 updates
  1. monitoring Dec 05, 2024, 08:06 PM UTC

    Deliveries might be delayed due to the tsunami warning affecting Northern California. There is currently no anticipated impact to the functionality of the Quartzy platform, otherwise.

  2. resolved Dec 05, 2024, 08:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 12, 2024

Service disruption

Detected by Pingoru
Aug 12, 2024, 11:00 PM UTC
Resolved
Aug 12, 2024, 11:42 PM UTC
Duration
42m
Affected: Quartzy Web ApplicationQuartzy Mobile ApplicationQuartzy Integrations
Timeline · 3 updates
  1. investigating Aug 12, 2024, 11:00 PM UTC

    We are currently investigating an inability to login for some users.

  2. monitoring Aug 12, 2024, 11:33 PM UTC

    We've identified, applied and are monitoring a fix

  3. resolved Aug 12, 2024, 11:42 PM UTC

    This incident has been resolved.

Read the full incident report →