All Systems Operational

ModernLoop Application Operational
90 days ago
99.98 % uptime
Today
ModernLoop - TaylorAI Operational
90 days ago
100.0 % uptime
Today
ModernLoop Homepage Operational
90 days ago
100.0 % uptime
Today
Login Operational
Auth0 User Authentication Operational
Auth0 Machine to Machine Authentication Operational
Cloud Hosting Operational
AWS EC2 Operational
AWS RDS Operational
AWS EKS Operational
AWS CloudWatch Operational
AWS GuardDuty Operational
AWS ELB Operational
Heroku Operational
Netlify High-Performance Edge Network Operational
Netlify Hosted DNS Operational
Email Notifications Operational
SendGrid API - Email Sends Operational
Integrations Operational
Google Apps Google Calendar Operational
Google Meet Operational
Slack API Operational
Zoom Developer Platform (APIs/Webhooks) Operational
Zoom Developer Platform (SDKs) Operational
Zoom Meetings Operational
Applicant Tracking System Partners Operational
90 days ago
96.0 % uptime
Today
Lever Hire Operational
Lever Integration API & Webhooks Operational
Lever Hire Operational
Lever Integration API & Webhooks Operational
Ashby API Operational
90 days ago
96.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Aug 9, 2026

No incidents reported today.

Aug 8, 2026

No incidents reported.

Aug 7, 2026

No incidents reported.

Aug 6, 2026

No incidents reported.

Aug 5, 2026

No incidents reported.

Aug 4, 2026

Resolved - The frontend build causing this issue has been reverted.
Aug 4, 09:28 PDT

Aug 3, 2026

Resolved - This incident has been resolved.
Aug 3, 10:56 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 3, 10:55 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 3, 10:42 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 3, 10:22 PDT
Identified - The issue has been identified and a fix is being implemented.
Aug 3, 10:08 PDT

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

No incidents reported.

Jul 30, 2026

No incidents reported.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

No incidents reported.

Jul 27, 2026

Resolved - This incident has been resolved.
Jul 27, 13:43 PDT
Investigating - We are currently investigating this issue.
Jul 27, 13:20 PDT

Jul 26, 2026

No incidents reported.