<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.maidcentral.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.maidcentral.com/history.atom"/>
  <title>MaidCentral Status - Incident history</title>
  <updated>2026-09-08T10:39:31.493+00:00</updated>
  <author>
    <name>MaidCentral</name>
  </author>
  
<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmtsjf6d507ga1bmr4ktum3k4</id>
  <published>2026-09-08T10:39:31.493+00:00</published>
  <updated>2026-09-08T10:39:31.493+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmtsjf6d507ga1bmr4ktum3k4"/>
  <title>Some users may see errors and slow load times</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> MaidCentral Web</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmtk35ad20v2p0wmvrimzazi4</id>
  <published>2026-09-01T20:00:00.000+00:00</published>
  <updated>2026-09-01T20:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmtk35ad20v2p0wmvrimzazi4"/>
  <title>QuickBooks sync was unavailable due to an Intuit outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours</p>
    <p><strong>Affected Components:</strong> QuickBooks Sync</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmtk3ajst000313nz3sgxvhkd</id>
  <published>2026-09-01T16:00:00.000+00:00</published>
  <updated>2026-09-01T16:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmtk3ajst000313nz3sgxvhkd"/>
  <title>Text message delivery was intermittently failing due to a Twilio outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> Text Messaging</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmsfedhqz037o1amme7rcb7uw</id>
  <published>2026-08-04T17:24:00.000+00:00</published>
  <updated>2026-08-04T17:24:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmsfedhqz037o1amme7rcb7uw"/>
  <title>Slower load times and errors for some users</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> MaidCentral Web</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmrdhx1vr00c50rs3gg9loqwj</id>
  <published>2026-06-22T11:30:00.000+00:00</published>
  <updated>2026-06-22T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmrdhx1vr00c50rs3gg9loqwj"/>
  <title>QuickBooks syncing delayed for one customer</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 14 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> QuickBooks Sync</p>
    <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&#039; 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&#039; limits, and verified sync error rates returned to normal. No customer data was affected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmqfn0b7f02h92oqtmo0n95ki</id>
  <published>2026-06-11T18:30:00.000+00:00</published>
  <updated>2026-06-11T18:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmqfn0b7f02h92oqtmo0n95ki"/>
  <title>Some QuickBooks customers were missing for some companies</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> MaidCentral Web</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.maidcentral.com,2005:Incident/cmrdi6epw071c0zlh0ndzi41v</id>
  <published>2026-06-08T19:37:00.000+00:00</published>
  <updated>2026-06-08T19:37:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.maidcentral.com/incident/cmrdi6epw071c0zlh0ndzi41v"/>
  <title>MaidCentral was slow for about an hour</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> MaidCentral Web</p>
    <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>

        ]]>
  </content>
</entry>

</feed>