MaidCentral Status - Incident history https://status.maidcentral.com MaidCentral Tue, 8 Sep 2026 10:39:31 +0000 Some users may see errors and slow load times Type: Incident Duration: 58 minutes Affected Components: MaidCentral Web Sep 8, 10:39:31 GMT+0 - Investigating - We are investigating errors and slow response times affecting some users and will update shortly. Sep 8, 11:37:40 GMT+0 - Resolved - This is resolved. Service is fully restored. Type: Incident

Duration: 58 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>10:39:31</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating errors and slow response times affecting some users and will update shortly..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>11:37:40</var> GMT+0</small><br><strong>Resolved</strong> - This is resolved. Service is fully restored..</p> ]]> Tue, 8 Sep 2026 10:39:31 +0000 https://status.maidcentral.com/incident/cmtsjf6d507ga1bmr4ktum3k4 https://status.maidcentral.com/incident/cmtsjf6d507ga1bmr4ktum3k4 QuickBooks sync was unavailable due to an Intuit outage Type: Incident Duration: 7 hours Affected Components: QuickBooks Sync Sep 1, 20:00:00 GMT+0 - Identified - QuickBooks sync was unavailable from 4:00 PM to 11:00 PM ET on Sept 1 due to an outage at Intuit. Invoice and tip sync to QuickBooks failed during this window and resumed automatically once Intuit recovered. No MaidCentral data was affected. Sep 2, 03:00:00 GMT+0 - Resolved - Intuit restored service at 11:00 PM ET and QuickBooks sync resumed automatically. Type: Incident

Duration: 7 hours

Affected Components:

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Identified</strong> - QuickBooks sync was unavailable from 4:00 PM to 11:00 PM ET on Sept 1 due to an outage at Intuit. Invoice and tip sync to QuickBooks failed during this window and resumed automatically once Intuit recovered. No MaidCentral data was affected..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Intuit restored service at 11:00 PM ET and QuickBooks sync resumed automatically..</p> ]]> Tue, 1 Sep 2026 20:00:00 +0000 https://status.maidcentral.com/incident/cmtk35ad20v2p0wmvrimzazi4 https://status.maidcentral.com/incident/cmtk35ad20v2p0wmvrimzazi4 Text message delivery was intermittently failing due to a Twilio outage Type: Incident Duration: 1 hour and 30 minutes Affected Components: Text Messaging Sep 1, 16:00:00 GMT+0 - Identified - Text message (SMS) delivery was intermittently failing from 12:00 PM to 1:30 PM ET on Sept 1 due to an outage at Twilio, our SMS provider. Some appointment reminders and text messages may have failed or been delayed during this window. No MaidCentral data was affected. Sep 1, 17:30:00 GMT+0 - Resolved - Twilio restored service at 1:30 PM ET and text message delivery returned to normal. Type: Incident

Duration: 1 hour and 30 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - Text message (SMS) delivery was intermittently failing from 12:00 PM to 1:30 PM ET on Sept 1 due to an outage at Twilio, our SMS provider. Some appointment reminders and text messages may have failed or been delayed during this window. No MaidCentral data was affected..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Resolved</strong> - Twilio restored service at 1:30 PM ET and text message delivery returned to normal..</p> ]]> Tue, 1 Sep 2026 16:00:00 +0000 https://status.maidcentral.com/incident/cmtk3ajst000313nz3sgxvhkd https://status.maidcentral.com/incident/cmtk3ajst000313nz3sgxvhkd Slower load times and errors for some users Type: Incident Duration: 29 minutes Affected Components: MaidCentral Web Aug 4, 17:24:00 GMT+0 - Identified - Between 1:24pm and 1:53pm ET on August 4, an administrative cleanup task held a database lock that slowed the app for many users. Time clock check-in and check-out was the most affected. The issue cleared on its own at 1:53pm ET and a fix is going to production tonight. Aug 4, 17:53:00 GMT+0 - Resolved - Service is fully restored. Type: Incident

Duration: 29 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>17:24:00</var> GMT+0</small><br><strong>Identified</strong> - Between 1:24pm and 1:53pm ET on August 4, an administrative cleanup task held a database lock that slowed the app for many users. Time clock check-in and check-out was the most affected. The issue cleared on its own at 1:53pm ET and a fix is going to production tonight..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>17:53:00</var> GMT+0</small><br><strong>Resolved</strong> - Service is fully restored..</p> ]]> Tue, 4 Aug 2026 17:24:00 +0000 https://status.maidcentral.com/incident/cmsfedhqz037o1amme7rcb7uw https://status.maidcentral.com/incident/cmsfedhqz037o1amme7rcb7uw QuickBooks syncing delayed for one customer Type: Incident Duration: 1 day, 14 hours and 8 minutes Affected Components: QuickBooks Sync Jun 22, 11:30:00 GMT+0 - Identified - QuickBooks syncing was delayed and some syncs failed for one customer whose sync volume exceeded QuickBooks' request limits. Other customers were not affected. Jun 24, 01:38:00 GMT+0 - Resolved - Fixed — we moved this syncing to a paced background process so it can no longer exceed QuickBooks' limits, and verified sync error rates returned to normal. No customer data was affected. Type: Incident

Duration: 1 day, 14 hours and 8 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Identified</strong> - QuickBooks syncing was delayed and some syncs failed for one customer whose sync volume exceeded QuickBooks' request limits. Other customers were not affected..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>01:38:00</var> GMT+0</small><br><strong>Resolved</strong> - Fixed — we moved this syncing to a paced background process so it can no longer exceed QuickBooks' limits, and verified sync error rates returned to normal. No customer data was affected..</p> ]]> Mon, 22 Jun 2026 11:30:00 +0000 https://status.maidcentral.com/incident/cmrdhx1vr00c50rs3gg9loqwj https://status.maidcentral.com/incident/cmrdhx1vr00c50rs3gg9loqwj Some QuickBooks customers were missing for some companies Type: Incident Affected Components: MaidCentral Web Jun 11, 18:30:00 GMT+0 - Investigating - We are investigating reports that some customers imported from QuickBooks are not appearing in customer lists for some companies. Jun 13, 03:00:00 GMT+0 - Resolved - We identified an issue where some of your customers from QuickBooks Online were not appearing in your account. QuickBooks sends us your customer list in batches. In certain cases, QuickBooks returned a batch that was smaller than the size it was asked for — an unexpected behavior on QuickBooks’ side. Because that short batch signaled there was no more data to send, the remaining customers weren’t pulled in during that sync. This only affected accounts with a large number of QuickBooks customers, and only when QuickBooks returned one of these unexpectedly short batches. Many partners were never affected. We’ve since strengthened how our integration handles QuickBooks’ batching so this can’t happen again. Type: Incident

Affected Components:

<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating reports that some customers imported from QuickBooks are not appearing in customer lists for some companies..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Resolved</strong> - We identified an issue where some of your customers from QuickBooks Online were not appearing in your account. QuickBooks sends us your customer list in batches. In certain cases, QuickBooks returned a batch that was smaller than the size it was asked for — an unexpected behavior on QuickBooks’ side. Because that short batch signaled there was no more data to send, the remaining customers weren’t pulled in during that sync. This only affected accounts with a large number of QuickBooks customers, and only when QuickBooks returned one of these unexpectedly short batches. Many partners were never affected. We’ve since strengthened how our integration handles QuickBooks’ batching so this can’t happen again..</p> ]]> Thu, 11 Jun 2026 18:30:00 +0000 https://status.maidcentral.com/incident/cmqfn0b7f02h92oqtmo0n95ki https://status.maidcentral.com/incident/cmqfn0b7f02h92oqtmo0n95ki MaidCentral was slow for about an hour Type: Incident Duration: 58 minutes Affected Components: MaidCentral Web Jun 8, 19:37:00 GMT+0 - Identified - MaidCentral pages loaded slowly or timed out starting around 3:37 PM ET. A behind-the-scenes maintenance task overran into business hours and crowded out customer work. Jun 8, 20:35:00 GMT+0 - Resolved - Resolved around 4:35 PM ET the same day. We replaced the maintenance task with a lighter nightly version that is hard-capped so it cannot run into business hours again. No customer data was affected. Type: Incident

Duration: 58 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>19:37:00</var> GMT+0</small><br><strong>Identified</strong> - MaidCentral pages loaded slowly or timed out starting around 3:37 PM ET. A behind-the-scenes maintenance task overran into business hours and crowded out customer work..</p> <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>20:35:00</var> GMT+0</small><br><strong>Resolved</strong> - Resolved around 4:35 PM ET the same day. We replaced the maintenance task with a lighter nightly version that is hard-capped so it cannot run into business hours again. No customer data was affected..</p> ]]> Mon, 8 Jun 2026 19:37:00 +0000 https://status.maidcentral.com/incident/cmrdi6epw071c0zlh0ndzi41v https://status.maidcentral.com/incident/cmrdi6epw071c0zlh0ndzi41v