Gitbook Status · History · Incident #124841

RESOLVED

GitBook webapp is returning 500

Critical · Started Jun 25, 2026 · 11:34 AM

Duration

1h 33m
Severity

Critical
Detection lead

—
User reports

—

Summary

GitBook webapp is returning 500

The incident has been resolved and systems are fully operational.

Started

Jun 25, 2026 · 11:34 AM
Resolved

Jun 25, 2026 · 1:08 PM
Duration

1h 33m
Severity

Critical

Event timeline

How this incident unfolded

◆

Identified
Jun 25 · 11:34 AM Gitbook

A faulty SQL migration caused a corrupted deployment. Our team is working on a fix.
◆

Identified
Jun 25 · 12:29 PM Gitbook

A fix is being deployed, we are monitoring the change.
◉

Monitoring
Jun 25 · 1:07 PM Gitbook

A fix has been released, and we're monitoring it
✓

Resolved
Jun 25 · 1:08 PM Gitbook

The incident has been resolved and systems are fully operational.

Pattern

Other recent incidents

Browse full incident history →

Get alerted before the next Gitbook outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start Monitoring Free