Green Cloud Technologies incident

ATL - IaaS Backups

Minor Resolved View vendor source →

Green Cloud Technologies experienced a minor incident on April 30, 2025 affecting IaaS - Atlanta, GA and DRaaS with Veeam - Atlanta, GA, lasting 16d 1h. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2025, 12:22 PM UTC
Resolved
May 16, 2025, 02:14 PM UTC
Duration
16d 1h
Detected by Pingoru
Apr 30, 2025, 12:22 PM UTC

Affected components

IaaS - Atlanta, GADRaaS with Veeam - Atlanta, GA

Update timeline

  1. investigating Apr 30, 2025, 12:22 PM UTC

    11:11's Cloud Infrastructure team is investigating an issue resulting in intermittently delayed or failed IaaS backups in the Atlanta data center. More details will be provided in updates as information becomes available.

  2. investigating May 02, 2025, 03:00 PM UTC

    Engineers are continuing to work with our vendor to identify and resolve the issues affecting a portion of IaaS backups in the Atlanta data center. During this time, customer backups may continue to be intermittently delayed or unable to complete. The next update will be posted as information becomes available.

  3. investigating May 02, 2025, 04:19 PM UTC

    11:11 engineers are also aware of intermittent degraded performance for IaaS in the Atlanta data center. Engineers are currently working with the vendor to resolve the issue.

  4. identified May 02, 2025, 06:28 PM UTC

    11:11 engineers worked with our vendor to identify and potentially resolve the issue causing degraded performance affecting a portion of IaaS backups in Atlanta. The team is continuing to monitor the environment for stability. Engineers identified the cause of the performance degradation in the IaaS environment in Atlanta and the team is continuing to work towards resolution. Customers may continue to see degraded performance as engineers work towards resolution. The next update will be posted as information becomes available.

  5. monitoring May 08, 2025, 01:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved May 16, 2025, 02:14 PM UTC

    This incident has been resolved.