Stacksync Outage History

Stacksync is up right now

Stacksync had 6 outages in the last 2 years totaling 17h 12m of downtime, averaging 0.2 incidents per month.

There were 6 Stacksync outages since October 22, 2024 totaling 17h 12m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.stacksync.com

Major February 6, 2026

Some managed databases have connectivity and cannot be reached

Detected by Pingoru
Feb 06, 2026, 07:42 PM UTC
Resolved
Feb 06, 2026, 09:40 PM UTC
Duration
1h 58m
Affected: Current status by service (Stacksync Databases)
Timeline · 2 updates
  1. investigating Feb 06, 2026, 07:42 PM UTC

    We're still trying to understand the root cause of the issue at the moment, this is not affecting all managed databases, only a handful of them.

  2. resolved Feb 06, 2026, 09:40 PM UTC

    We've identified this problem, and believe negative caching of DNS records to be all that remains. We are going to continue to check for at least thirty minutes, the longest time reported for negative caching so far.

Read the full incident report →

Major October 20, 2025

Downtime affecting several services

Detected by Pingoru
Oct 20, 2025, 07:11 AM UTC
Resolved
Oct 20, 2025, 08:52 PM UTC
Duration
13h 41m
Affected: Current status by service (Stacksync Syncs)
Timeline · 2 updates
  1. investigating Oct 20, 2025, 07:11 AM UTC

    We are currently experiencing downtime due to outages impacting multiple critical AWS services. Our engineering team is fully engaged and working diligently to restore full functionality as quickly as possible. Please note that the web browser application and the US-NV region are temporarily unavailable, while data synchronization operations in the Belgium Stacksync region remain fully operational.

  2. resolved Oct 20, 2025, 08:52 PM UTC

    All services are now fully operational, and data backfilling is in progress to ensure complete synchronization.

Read the full incident report →

Minor April 11, 2025

Downtime

Detected by Pingoru
Apr 11, 2025, 03:59 PM UTC
Resolved
Apr 11, 2025, 04:12 PM UTC
Duration
13m
Affected: Current status by service (Stacksync Syncs)
Timeline · 2 updates
  1. investigating Apr 11, 2025, 03:59 PM UTC

    Data syncing are currently temporary being on hold.

  2. resolved Apr 11, 2025, 04:12 PM UTC

    The syncing is restarting now. All events that could not be processed are going to be processed and no events have been lost, only delayed.

Read the full incident report →

Minor January 16, 2025

Downtime Belgium region

Detected by Pingoru
Jan 16, 2025, 03:32 PM UTC
Resolved
Jan 16, 2025, 04:05 PM UTC
Duration
33m
Affected: Current status by service (Stacksync Syncs)
Timeline · 2 updates
  1. investigating Jan 16, 2025, 03:32 PM UTC

    Downtime Belgium region

  2. resolved Jan 16, 2025, 04:05 PM UTC

    Downtime Belgium region ended.

Read the full incident report →

Minor December 10, 2024

Downtime USNV region

Detected by Pingoru
Dec 10, 2024, 08:18 AM UTC
Resolved
Dec 10, 2024, 08:53 AM UTC
Duration
35m
Affected: Current status by service (Stacksync Syncs)
Timeline · 2 updates
  1. investigating Dec 10, 2024, 08:18 AM UTC

    Downtime USNV region

  2. resolved Dec 10, 2024, 08:53 AM UTC

    situation resolved

Read the full incident report →

Major October 22, 2024

Belgium region downtime

Detected by Pingoru
Oct 22, 2024, 02:29 PM UTC
Resolved
Oct 22, 2024, 02:41 PM UTC
Duration
12m
Affected: Current status by service (Stacksync Syncs)
Timeline · 2 updates
  1. investigating Oct 22, 2024, 02:29 PM UTC

    Belgium region unavailable due to network issues.

  2. resolved Oct 22, 2024, 02:41 PM UTC

    Traffic has been redirected, issue is fixed.

Read the full incident report →