Aug <var data-var='date'>20</var>, <var data-var='time'>18:05</var> PDT Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>09:46</var> PDT Monitoring - Monitoring — Slow loading of task pages, the dashboard, and scheduling, and intermittent timeouts, have been resolved. Starting at 10:15 UTC (3:15 AM PT), a subset of customers experienced slow page loads and occasional timeouts when opening task pages, the Upcoming Events dashboard, Reporting, and the scheduling flow. The public API and MCP integrations could also return timeout errors during this period. No data was lost, and no scheduled interviews were affected. We identified the cause: a database read path that, for some accounts, repeated the same large query many times in a single request and kept running after the request had already timed out. This placed sustained load on our read database replicas. We deployed a fix at 15:20 UTC (8:20 AM PT) that limits that path, and response times returned to normal by 16:00 UTC (9:00 AM PT). We are monitoring the platform closely while the remaining database load returns to normal, and we are rolling out additional safeguards so that a single request can no longer create this kind of load. We will post a final update once monitoring is complete. We apologize for the disruption. Aug <var data-var='date'>20</var>, <var data-var='time'>07:36</var> PDT Update - We are continuing to investigate this issue. Aug <var data-var='date'>20</var>, <var data-var='time'>07:36</var> PDT Investigating - We are currently investigating this issue.

ModernLoop Slowness

Aug <var data-var='date'> 4</var>, <var data-var='time'>09:28</var> PDT Resolved - The frontend build causing this issue has been reverted.

"Something went wrong"

Aug <var data-var='date'> 3</var>, <var data-var='time'>10:56</var> PDT Resolved - This incident has been resolved. Aug <var data-var='date'> 3</var>, <var data-var='time'>10:55</var> PDT Update - # Elevated error rates on some read operations — August 3, 2026 **Status:** Resolved **Duration:** 16:43 – 17:38 UTC (approximately 55 minutes) ## Summary On August 3, 2026, between 16:43 and 17:38 UTC, some customers experienced intermittent errors and slow responses on a subset of read operations, including loading team member directories, viewing scheduling suggestions, and loading metrics dashboards. Scheduling data and all previously saved information were unaffected, and no data was lost. Retrying the affected pages generally succeeded once the incident resolved. ## What happened A routine database maintenance operation performed during a scheduled deployment placed unusually high load on our database infrastructure. This temporarily delayed our read-replica databases, causing a portion of read queries to time out or be cancelled while the replicas caught up. The initial recovery at 17:15 UTC was followed by a second period of elevated errors while database read traffic rebalanced; error rates fully returned to normal at approximately 17:38 UTC. ## Impact - A subset of read requests failed or responded slowly during the incident window. Affected requests returned errors and could be retried. - Some customers were temporarily unable to create new schedules during the incident window; those attempts succeeded once the incident resolved. Previously created schedules, tasks, and candidate data were unaffected. - No data was lost or corrupted. ## What we're doing to prevent this - Scheduling large database maintenance operations outside of peak usage hours. - Adding automatic retries for the class of transient read errors seen during this incident, so brief replication delays no longer surface as user-facing errors. - Adding earlier alerting on database replication delay so we can respond before customers are impacted. - Optimizing the specific queries that were most affected so they are more resilient to brief periods of database pressure. We apologize for the disruption. If you continue to see errors, please contact support@modernloop.io. Aug <var data-var='date'> 3</var>, <var data-var='time'>10:42</var> PDT Monitoring - A fix has been implemented and we are monitoring the results.

Issues creating schedules

Aug <var data-var='date'> 3</var>, <var data-var='time'>10:22</var> PDT Resolved - # Elevated error rates on some read operations — August 3, 2026 **Status:** Resolved **Duration:** 16:43 – 17:15 UTC (approximately 32 minutes) ## Summary On August 3, 2026, between 16:43 and 17:15 UTC, some customers experienced intermittent errors and slow responses on a subset of read operations, including loading team member directories, viewing scheduling suggestions, and loading metrics dashboards. Scheduling data and all previously saved information were unaffected, and no data was lost. Retrying the affected pages generally succeeded once the incident resolved. ## What happened A routine scheduled deployment placed unusually high load on our database infrastructure. This temporarily delayed our read-replica databases, causing a portion of read queries to time out or be cancelled while the replicas caught up. Error rates returned to normal at approximately 17:15 UTC once the maintenance operation completed and replication fully recovered. ## Impact - A subset of read requests failed or responded slowly during the incident window. Affected requests returned errors and could be retried. - Write operations (creating and updating schedules, tasks, and candidate data) were not materially affected. - No data was lost or corrupted. ## What we're doing to prevent this - Adding automatic retries for the class of transient read errors seen during this incident, so brief replication delays no longer surface as user-facing errors. - Adding earlier alerting on database replication delay so we can respond before customers are impacted. - Optimizing the specific queries that were most affected so they are more resilient to brief periods of database pressure. We apologize for the disruption. If you continue to see errors, please contact support@modernloop.io. Aug <var data-var='date'> 3</var>, <var data-var='time'>10:08</var> PDT Identified - The issue has been identified and a fix is being implemented.

Reports of Slowness

Jul <var data-var='date'>27</var>, <var data-var='time'>13:43</var> PDT Resolved - This incident has been resolved. Jul <var data-var='date'>27</var>, <var data-var='time'>13:20</var> PDT Investigating - We are currently investigating this issue.

Reports of slowness on ModernLoop App

Jul <var data-var='date'>14</var>, <var data-var='time'>15:12</var> PDT Resolved - This incident has been resolved. Jul <var data-var='date'>14</var>, <var data-var='time'>12:21</var> PDT Identified - Reports of schedule tasks in incorrect status buckets. Otherwise schedule tasks are fully functional.

Schedule Tasks in incorrect status bucket

Jul <var data-var='date'>14</var>, <var data-var='time'>12:19</var> PDT Resolved - While the Ashby APIs are not improved, ModernLoop has put extensive work into handling the errors via sophisticated retry logic. Closing this out for now, to reduce noise on our Status Page. Will report with more data once the Ashby team relays their fixes. Jul <var data-var='date'> 4</var>, <var data-var='time'>21:14</var> PDT Investigating - If you do not use Ashby ATS you are unaffected. Ashby Scheduling API Timeout on 5% Creates and 33% Updates causing mismatches in what is live on ModernLoop vs Ashby. Ashby has identified some areas for improvements and is implementing.

Ashby Scheduling API Timeouts on 5% Creates and 33% Updates

Jun <var data-var='date'>25</var>, <var data-var='time'>16:05</var> PDT Resolved - This incident has been resolved. Jun <var data-var='date'>25</var>, <var data-var='time'>16:03</var> PDT Identified - The issue has been identified and a fix is being implemented.

Task Requirements Error

Jun <var data-var='date'>23</var>, <var data-var='time'>16:07</var> PDT Resolved - We identified an issue that caused some users to be logged out. The affected version has been rolled back — please refresh the page and log in again to continue. Jun <var data-var='date'>23</var>, <var data-var='time'>16:00</var> PDT Investigating - We are currently investigating this issue.

Users being logged out

Jun <var data-var='date'>18</var>, <var data-var='time'>23:56</var> PDT Resolved - This incident has been resolved. Jun <var data-var='date'>18</var>, <var data-var='time'>12:42</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>18</var>, <var data-var='time'>12:11</var> PDT Investigating - We are currently investigating this issue.

Reports of Task views not loading

Apr <var data-var='date'>17</var>, <var data-var='time'>10:20</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>17</var>, <var data-var='time'>09:53</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>17</var>, <var data-var='time'>09:42</var> PDT Investigating - We are currently investigating this issue.

Reports of ModernLoop Slowness

Jan <var data-var='date'>20</var>, <var data-var='time'>20:53</var> PST Resolved - # Root Cause Analysis (RCA) Date: January 20, 2026 Status: Resolved ## Summary On January 20, 2026, we experienced a prolonged service disruption during a backend infrastructure upgrade intended to improve system capacity. While the upgrade was expected to cause only a brief interruption, an issue during the cloud provider’s upgrade process prevented the database from completing its automatic failover, extending the impact. No customer data was lost or corrupted, and full service has been restored. ## What Happened Earlier in the day, increased traffic caused elevated load on a backend database component, resulting in degraded performance. To address this, we initiated a capacity upgrade designed to improve stability and prevent further impact. During the upgrade, an internal failure occurred within the cloud provider’s managed database service. This failure prevented the database from completing its expected automatic failover. As a result, the system became unavailable for write operations longer than anticipated. The upgrade process became stuck mid-operation and required direct intervention from the cloud provider (AWS) to safely complete. ## Impact to Customers • Customers experienced service interruptions and were unable to perform write actions (such as updates or changes). • Candidates were not able to submit availability nor submit schedules • The disruption lasted longer than expected due to the failed upgrade process. • No customer data that was entered to the system was lost, corrupted, or exposed. ## Timeline (2026-01-20) • 9:00am PST - Replication lag cyclical pattern began on instance-3 • 12:04pm PST - Peak disk queue depth observed on instance-3 (114.34) • 12:13pm PST - Instance-2 began showing elevated disk queue depth • 12:57am PST - Root cause identified as instance class limitation • ~2:00pm PST - Remediation initiated: Instance class upgrade to db.r6gd.xlarge started • ~2:30 PST - Escalation: Database upgrade failed; site entered read-only mode • ~3:00 PST - Escalation: AWS Business Support engaged • ~6:30 PST - Service restored: Site returned to full read/write capability • ~19:30 PST - Full recovery: Backend workers scaled back to full capacity • ~20:00 PST - Incident closed; monitoring confirmed stable operations ## Root Cause The root cause was a combination of increased system load and a failure during a managed database upgrade performed by our cloud provider. While the upgrade was intended to be low-impact, the provider’s automation became stuck mid-process, preventing timely recovery. ## Resolution We worked directly with our cloud provider to diagnose and resolve the failed upgrade. Once the issue was corrected, database services resumed normal operation and system performance stabilized. ## Preventive Actions To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: • Increasing baseline capacity and operational headroom to better absorb traffic spikes. • Improving detection and alerting for early signs of resource saturation. • Enhancing safeguards and runbooks for infrastructure changes under load. • Working with our cloud provider to review failure scenarios and escalation procedures for managed service upgrades. ## Current Status All services are fully operational and performing normally. We continue to monitor the system closely. We take responsibility for the availability of our service and regret the extended disruption. While part of the incident involved a cloud provider failure, we are applying the lessons learned to further strengthen reliability going forward. Thank you for your patience. Jan <var data-var='date'>20</var>, <var data-var='time'>16:07</var> PST Update - Our infrastructure upgrade is taking longer than expected due to a backend synchronization step. We’re actively working with our cloud provider to complete the upgrade safely. No customer data is at risk. Jan <var data-var='date'>20</var>, <var data-var='time'>14:52</var> PST Identified - Increased demand caused performance degradation in a backend service. We’re scaling system capacity to resolve the issue and prevent recurrence. A short interruption may occur during the upgrade. Jan <var data-var='date'>20</var>, <var data-var='time'>11:01</var> PST Update - We are continuing to investigate this issue. Jan <var data-var='date'>20</var>, <var data-var='time'>10:41</var> PST Update - We are continuing to investigate this issue. Jan <var data-var='date'>20</var>, <var data-var='time'>10:40</var> PST Investigating - We are currently investigating this issue.

ModernLoop and Candidate Portal - Slow and/or Down

Aug <var data-var='date'>26</var>, <var data-var='time'>12:12</var> PDT Resolved - Root cause: Not enough servers to handle daily load. Latency would spike during the middle of the day (12pm-1pm PST). ModernLoop infra has been scaled up significantly. We expect this to be a permanent change. Apologies for the inconvenience as we diagnosed this issue. Aug <var data-var='date'>25</var>, <var data-var='time'>14:59</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>25</var>, <var data-var='time'>14:53</var> PDT Investigating - We are currently investigating this issue. Aug <var data-var='date'>25</var>, <var data-var='time'>14:43</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>25</var>, <var data-var='time'>14:33</var> PDT Investigating - We are currently investigating this issue.

Aug <var data-var='date'>18</var>, <var data-var='time'>14:51</var> PDT Resolved - This incident has been resolved. Aug <var data-var='date'>18</var>, <var data-var='time'>13:01</var> PDT Investigating - We are currently investigating this issue.

Aug <var data-var='date'>15</var>, <var data-var='time'>10:51</var> PDT Resolved - This incident has been resolved. Aug <var data-var='date'>15</var>, <var data-var='time'>10:39</var> PDT Investigating - We are currently investigating this issue.

ModernLoop Servers Not Responding

Aug <var data-var='date'>13</var>, <var data-var='time'>10:07</var> PDT Resolved - This incident has been resolved. Servers were erroneously restarting without a proper cooldown. The ModernLoop team has implemented a fix. Aug <var data-var='date'>13</var>, <var data-var='time'>10:01</var> PDT Update - We are continuing to investigate this issue. Aug <var data-var='date'>13</var>, <var data-var='time'>09:58</var> PDT Investigating - We are currently investigating this issue.

Slowness in the application

May <var data-var='date'>29</var>, <var data-var='time'>13:34</var> PDT Resolved - This incident has been resolved. May <var data-var='date'>29</var>, <var data-var='time'>13:16</var> PDT Investigating - We are currently investigating this issue.

Reports of slowness

Apr <var data-var='date'>16</var>, <var data-var='time'>19:51</var> PDT Resolved - https://status.zoom.us/incidents/pw9r9vnq5rvk Apr <var data-var='date'>16</var>, <var data-var='time'>12:21</var> PDT Identified - Zoom Official Status Pages (may not load) https://status.zoom.us/ https://uptime.zoom.us/ ~50K people reporting Zoom is down for them in the last hour https://downdetector.com/status/zoom/

Zoom is down

Mar <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> PST Resolved - Due to a version upgrade for our email service, some emails sent through gmail failed to deliver between 3/3 10pm PST - 3/4 7am PST

GMail email sends sporadically failing

Mar <var data-var='date'> 2</var>, <var data-var='time'>10:00</var> PST Completed - The scheduled maintenance has been completed. Mar <var data-var='date'> 2</var>, <var data-var='time'>03:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>25</var>, <var data-var='time'>14:41</var> PST Scheduled - We will be migrating our search workloads to a new search cluster. Intermittent slowness and stale data is possible.

Search Infra Maintenance

Feb <var data-var='date'>26</var>, <var data-var='time'>17:16</var> PST Resolved - This incident has been resolved. Feb <var data-var='date'>26</var>, <var data-var='time'>17:15</var> PST Update - We are continuing to investigate this issue. Feb <var data-var='date'>26</var>, <var data-var='time'>08:18</var> PST Investigating - Slack is down: https://slack-status.com/2025-02/1b757d1d0f444c34

Slack is down

Feb <var data-var='date'>18</var>, <var data-var='time'>13:53</var> PST Resolved - See resolution here: https://status.lever.co/incidents/r94mjyqwbxtv Feb <var data-var='date'>18</var>, <var data-var='time'>09:27</var> PST Identified - ModernLoop team is following along here: https://status.lever.co/incidents/r94mjyqwbxtv This does not affect customers on other Applicant Tracking Systems.

Lever Hire Platform is returning 500 error

Feb <var data-var='date'>12</var>, <var data-var='time'>13:43</var> PST Resolved - This incident has been resolved. Feb <var data-var='date'>12</var>, <var data-var='time'>12:40</var> PST Update - This incident has been resolved. And we are continuing to monitor. Feb <var data-var='date'>12</var>, <var data-var='time'>12:32</var> PST Investigating - We are currently investigating this issue.

ML Slowness

Feb <var data-var='date'>12</var>, <var data-var='time'>10:03</var> PST Resolved - This incident has been resolved. Feb <var data-var='date'>12</var>, <var data-var='time'>09:54</var> PST Investigating - We are currently investigating this issue.

Site Not Loading

Feb <var data-var='date'> 5</var>, <var data-var='time'>04:19</var> PST Resolved - The issue was due to a combination of hitting our IP address limit for our Kubernetes deployment and a bad version number for our Datadog Java Agent. Datadog Java Agent is 1.46.0 on Maven but that version doesn't not exist on Google Cloud Console Artifact Registry. The incorrect version prevented new pods from starting up and the ip address allocation prevented proper visibility into this issue. Followups include: * Adding a new subnet to increase the number of IPs * Add a CI check to make sure the JAR artifact exists for the Datadog Agent Library we need Feb <var data-var='date'> 5</var>, <var data-var='time'>03:45</var> PST Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'> 5</var>, <var data-var='time'>03:22</var> PST Investigating - We are currently investigating this issue.

Is ModernLoop down?

ModernLoop status is UP

Lastest published events

ModernLoop Slowness

"Something went wrong"

Issues creating schedules

ModernLoop Services, Components and Regions

Recent ModernLoop events

ModernLoop Slowness

"Something went wrong"

Issues creating schedules

Reports of Slowness

Reports of slowness on ModernLoop App

Schedule Tasks in incorrect status bucket