Marloo

Updates

• Jun 29, 2026 1:50 AM UTC

  This incident is resolved. Marloo recovered at approximately 1:00 PM NZST and has been stable since. For about an hour, between roughly 12:00 and 1:00 PM NZST, customers in Australia experienced slowness and intermittent errors caused by a backend capacity limit reached during a surge in background processing. We deployed a configuration change that restored normal performance. No customer data was affected. We are putting additional safeguards in place to prevent a recurrence, and we apologise for the disruption.

  Resolved
• Jun 29, 2026 1:29 AM UTC (21 minutes earlier)

  This incident is resolved. Marloo recovered at approximately 1:00 PM NZST and has been stable since. For about an hour, between roughly 12:00 and 1:00 PM NZST, customers in Australia experienced slowness and intermittent errors caused by a backend capacity limit reached during a surge in background processing. We deployed a configuration change that restored normal performance. No customer data was affected. We are putting additional safeguards in place to prevent a recurrence, and we apologise for the disruption.

  Resolved
• Jun 29, 2026 12:57 AM UTC (32 minutes earlier)

  We have deployed a fix and Marloo is recovering. We are monitoring closely to confirm it is fully stable.

  Monitoring
• Jun 29, 2026 12:10 AM UTC (47 minutes earlier)

  We are investigating reports of Marloo running slowly and occasionally returning errors for customers in Australia. Our engineering team is actively working on it.

  Investigating