Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Nov 4, 2026

  1. GitBookSecurity incident impacting published sites and GitBook app

    As promised, now that the incident is resolved, we’ve published our full post-mortem on the recent security incident. Read the full post-mortem: https://www.gitbook.com/status/security-incident-2026-11-03 The post explains what happened, a full timeline, exactly which customer data was accessible, how we responded to protect our customers, and what we’re doing next. We apologize again for the disruption. We hold ourselves to the highest standards, and we know an incident like this affects the trust you place in GitBook. We hope the transparency in this post-mortem, our previous communications, and the actions we’ve taken help rebuild it. If you have questions, contact your account manager or reply to this email to speak to our support team. For live updates, visit status.gitbook.com: http://status.gitbook.com. Sara Tandowsky, GitBook CEO Samy Pessé, GitBook Co-founder & CTO

    Resolved

  2. SentryIngestion delays across all data

    The issue causing ingestion delays in our US region has been resolved, all data has been backfilled and latency has returned to normal.

    Resolved

  3. GitHubIncident with Actions

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Resolved

  4. GitHubIncident with Actions and Pages

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Resolved

  5. MailerLiteTemporary service issues

    This incident has been resolved. All systems are back to normal operations. We apologize for any inconvenience caused and appreciate your patience. A full post-mortem/internal review will be conducted to prevent future occurrences.

    Resolved

  6. OVHcloud - Public Cloud[DE1][Network] - Load Balancer incident notification

    We would like to inform you that the incident affecting our Public Cloud Network offering in the DE1 region has now been resolved. Please find the details of this incident below : <b>Start time :</b> 04/11/2026 05:30 UTC <b>End time :</b> 04/11/2026 16:30 UTC <b>Impacted Service(s) :</b> The Network API in the DE1 region was temporarily unstable. Creation or modification of Load Balancers may have encountered issues. <b>Customers Impact :</b> Customers may have experienced API errors when performing network administrative actions, and were temporarily unable to create or resize their Load Balancers. Running services remained unaffected. <b>Root Cause :</b> This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

    Resolved

  7. SendGridRateQueue Host Down Did Not Recover

    Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

    No longer active

  8. TwilioRateQueue Host Down Did Not Recover

    Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

    No longer active

Older incidents