<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>MaidCentral Status - Incident history</title>
    <link>https://status.maidcentral.com</link>
    <description>MaidCentral</description>
    <pubDate>Mon, 22 Jun 2026 11:30:00 +0000</pubDate>
    
<item>
  <title>QuickBooks syncing delayed for one customer</title>
  <description>
    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&#039; 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&#039; limits, and verified sync error rates returned to normal. No customer data was affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 14 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  QuickBooks syncing was delayed and some syncs failed for one customer whose sync volume exceeded QuickBooks&#039; request limits. Other customers were not affected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 22 Jun 2026 11:30:00 +0000</pubDate>
  <link>https://status.maidcentral.com/incident/cmrdhx1vr00c50rs3gg9loqwj</link>
  <guid>https://status.maidcentral.com/incident/cmrdhx1vr00c50rs3gg9loqwj</guid>
</item>

<item>
  <title>Some QuickBooks customers were missing for some companies</title>
  <description>
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating reports that some customers imported from QuickBooks are not appearing in customer lists for some companies..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 11 Jun 2026 18:30:00 +0000</pubDate>
  <link>https://status.maidcentral.com/incident/cmqfn0b7f02h92oqtmo0n95ki</link>
  <guid>https://status.maidcentral.com/incident/cmqfn0b7f02h92oqtmo0n95ki</guid>
</item>

<item>
  <title>MaidCentral was slow for about an hour</title>
  <description>
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:37:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 8 Jun 2026 19:37:00 +0000</pubDate>
  <link>https://status.maidcentral.com/incident/cmrdi6epw071c0zlh0ndzi41v</link>
  <guid>https://status.maidcentral.com/incident/cmrdi6epw071c0zlh0ndzi41v</guid>
</item>

  </channel>
  </rss>