Rocket.net incident

Frankfurt Region Service Investigation

Major Resolved View vendor source →

Rocket.net experienced a major incident on July 13, 2026, lasting 1d 1h. The incident has been resolved; the full update timeline is below.

Started
Jul 13, 2026, 07:18 AM UTC
Resolved
Jul 14, 2026, 08:54 AM UTC
Duration
1d 1h
Detected by Pingoru
Jul 13, 2026, 07:18 AM UTC

Update timeline

  1. investigating Jul 13, 2026, 07:18 AM UTC

    We are currently investigating an issue affecting services in the Frankfurt region. Our engineering team is actively working to identify the cause and restore normal service. We will provide updates as more information becomes available.

  2. investigating Jul 13, 2026, 07:50 AM UTC

    A fix has been identified and applied. Services in the Frankfurt region are currently recovering, and we are monitoring the environment closely as systems return to normal operation. We will continue to provide updates as recovery progresses and confirm once the issue is fully resolved. Thank you for your patience and understanding.

  3. investigating Jul 13, 2026, 10:33 AM UTC

    We are continuing to investigate the issue affecting the Frankfurt region. Our engineering team is actively working to identify the cause and restore normal service. We understand the impact this is having and are treating this as a priority. We will continue monitoring the situation closely and provide further updates as soon as more information becomes available. Thank you for your patience and understanding.

  4. investigating Jul 13, 2026, 01:36 PM UTC

    Our team is still working to resolve issues affecting Frankfurt 30. We sincerely appreciate your patience in the meantime.

  5. investigating Jul 13, 2026, 03:53 PM UTC

    Thank you for your continued patience. Recovery efforts are still underway, and our team is working tirelessly until this is resolved.

  6. resolved Jul 14, 2026, 08:54 AM UTC

    The service disruption affecting the Frankfurt 30 node has been fully resolved. Our Engineering team has completed the necessary recovery actions, and affected services have returned to normal operation. We are continuing to monitor the environment closely to ensure stability and will investigate any remaining isolated issues if reported. We apologize for the disruption and appreciate the patience and understanding of our customers while we worked to restore service.