Gitbook logo
ALL SYSTEMS OPERATIONAL

Gitbook systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Sep 2025 · 15 incidents caught

Last checked: 5 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Gitbook is up and running.

    Last incident resolved 1 week ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked Gitbook. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds, so the next answer arrives by email.

10 monitors free, email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

90-Day Health Summary

  • Total Incidents

    4

    Jun 19 to Sep 17, 2026

  • Major / Critical

    3

    75% of the total

  • Minor Incidents

    1

    Avg. 0.0 per day

  • Median Resolution

    1h 24m

    P95: 7h 18m

Gitbook Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
App and published docs unavailable
Sep 5, 2026 · 6:56 PM 4m
Critical
Resolved
Details →
GitHub outage affecting Git Sync
Aug 17, 2026 · 1:56 PM 7h 18m
Minor
Resolved
Details →
GitBook webapp is returning 500
Jun 25, 2026 · 11:34 AM 1h 33m
Critical
Resolved
Details →
Sites are failing intermittently with 500 Internal Server Error
Jun 22, 2026 · 2:58 PM 1h 16m
Major
Resolved
Details →
Increased API error rate
Jun 2, 2026 · 2:40 PM 1h 28m
Major
Resolved
Details →
Degraded database performance
May 8, 2026 · 3:52 PM 2h 22m
Major
Resolved
Details →
500 errors on some *.gitbook.io published sites
May 4, 2026 · 11:55 AM 2h 4m
Major
Resolved
Details →
Git Sync executions are delayed due to third-party outage
Apr 15, 2026 · 3:34 PM 13h 22m
Major
Resolved
Details →
Degraded API performance
Mar 27, 2026 · 2:43 PM 4h 4m
Major
Resolved
Details →
Documentation sites with a custom domain returned a 404 error
Mar 6, 2026 · 4:56 PM 2h 20m
Major
Resolved
Details →

How do they compare?

Alternatives to Gitbook

Common questions

Frequently Asked Questions

  • Is Gitbook down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Gitbook go down?

    Based on our 90-day data, we've detected 4 incidents, of which 3 were major or critical. The median resolution time is 1h 24m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.