Exalate incident

Github Sync Blocking Errors

Major Resolved View vendor source →

Exalate experienced a major incident on February 26, 2024 affecting Exalate for GitHub, lasting 9d 13h. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2024, 05:02 PM UTC
Resolved
Mar 07, 2024, 06:43 AM UTC
Duration
9d 13h
Detected by Pingoru
Feb 26, 2024, 05:02 PM UTC

Affected components

Exalate for GitHub

Update timeline

  1. identified Feb 26, 2024, 05:02 PM UTC

    Issue: Exalate for Github users may encounter errors that block outgoing synchronisation. Status: We have identified the root cause (there's recent change in the Github Webhook format affecting Exalate sync) and we are actively working on a solution to restore normal sync operations. Action Required: No actions are required from users at this time. We apologize for any inconvenience caused and appreciate your patience as we work to resolve this issue promptly. We will provide further updates as soon as the situation progresses. Thank you for your understanding.

  2. identified Feb 26, 2024, 07:29 PM UTC

    Fix Development in Progress Update: The fix for the reported issue is ready and undergoing final preparations before deployment on all affected instances. Current Status: We're ensuring a smooth fix process across all affected nodes. Action Required: For urgent help, please create a ticket on our Support Portal. Our Support team is ready to assist you. Thank you for your patience. Further updates are expected at Feb 27, 9AM CET

  3. identified Feb 27, 2024, 07:57 AM UTC

    Fix version is undergoing final tests. Update: The fix for the reported issue is in testing. Current Status: The deployment of the fix is scheduled for later today. Action Required: No actions are required from users at this time. Thank you for your patience. Further updates are expected at 13:00 CET

  4. identified Feb 27, 2024, 11:56 AM UTC

    Fix version is scheduled for deployment. Update: The fix for the reported issue is going to be deployed at 14:00 CET on all Github nodes. Action Required: No actions are required from users at this time. Thank you for your patience.

  5. monitoring Feb 28, 2024, 07:34 AM UTC

    The fix has been deployed on all affected instances, we are now monitoring for any errors.

  6. resolved Mar 07, 2024, 06:43 AM UTC

    The solution has been applied successfully, the incident has been resolved. Please contact our support if you have any questions or comments.

  7. postmortem Apr 01, 2026, 04:12 AM UTC

    timeout