EstateSync Outage History

EstateSync is up right now

EstateSync had 3 outages in the last 2 years totaling 21h 18m of downtime — averaging 0.1 incidents per month.

There were 3 EstateSync outages since September 18, 2024 totaling 21h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.estatesync.com

Minor April 15, 2026

Processing of publications ...

Detected by Pingoru
Apr 15, 2026, 06:12 PM UTC
Resolved
Apr 16, 2026, 10:17 AM UTC
Duration
16h 5m
Affected: Current status by service (API)
Timeline · 2 updates
  1. investigating Apr 15, 2026, 06:12 PM UTC

    Due to a bug, internal email processing of import reports is delayed. Some properties might still appear as processing for a longer time than usual. Their status will be resolved within the next few hours. Need help? Contact us at [email protected].

  2. resolved Apr 16, 2026, 10:17 AM UTC

    The issue has beed identified and resolved. Some properties might still appear as processing for longer times than usual. Their status will be resolved within the next few hours. Need help? Contact us at [email protected].

Read the full incident report →

Major February 15, 2026

API is down

Detected by Pingoru
Feb 15, 2026, 08:58 AM UTC
Resolved
Feb 15, 2026, 08:59 AM UTC
Duration
1m
Affected: Current status by service (API)
Timeline · 2 updates
  1. investigating Feb 15, 2026, 08:58 AM UTC

    API went down.

  2. resolved Feb 15, 2026, 08:59 AM UTC

    API recovered.

Read the full incident report →

Minor May 7, 2025

Latency and Errors in API

Detected by Pingoru
May 07, 2025, 03:33 AM UTC
Resolved
May 07, 2025, 08:45 AM UTC
Duration
5h 12m
Affected: Current status by service (API)
Timeline · 2 updates
  1. investigating May 07, 2025, 03:33 AM UTC

    The EstateSync API is currently experiencing issues with reachability. We are in the process of investigating the problem.

  2. resolved May 07, 2025, 08:45 AM UTC

    The incident has been resolved! The reachability problems were caused by a issue of our cloud provider Google Cloud in the Frankfurt region. We will continue to monitor ongoing operations.

Read the full incident report →