Re:Gitbook Breached
by petecooper on Tuesday November 03, 2026 @12:09PM
(#50354717)
https://www.gitbook.com/status/security-incident-2026-11-03
[ Parent
| on HN ]
Re:Gitbook Breached
by philipwhiuk on Tuesday November 03, 2026 @01:02PM
(#50355616)
It's bizarre they have both this and gitbookstatus.com and they contain different info.
We summarized more information on this page from recent learnings, than what has been posted as updates on the status page (https://www.gitbookstatus.com/incidents/01M6FXDDGQRWHMYYWXY2...).
Re:Gitbook Breached
by philipwhiuk on Friday November 06, 2026 @01:09PM
(#50396019)
Just to be clear you have:
* https://www.gitbook.com/status
* https://www.gitbookstatus.com/
You get why this is confusing, right?
the classic failure mechanism in the status page
Re:Gitbook Breached
by eddythompson80 on Tuesday November 03, 2026 @01:43PM
(#50356289)
Does a security incident page really need to connect to 11 3rd party domains. smh
If it was made by a web designer, then yes. It's also nice to have 151 HTML warnings and errors:
https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.gitbook.c...
And images that are 4x larger than necessary on the main page (nevermind whether the images add value to begin with):
https://webspeedtest.cloudinary.com/results/261104_YiDc1V_1W
There are maybe 10 websites that look good "inside and out" because web design is a broken field run by non-technical people.
I wanna note that some (52) of those are
"css property corner-shape doesn't exist", and it does, just isn't supported in all browsers yet.
Re:Gitbook Breached
by tmp219380123809 on Wednesday November 04, 2026 @04:50PM
(#50372051)
That isn't a dedicated security status page, it's their main website.
The actual status page appears to be hosted on incident.io https://www.gitbookstatus.com/incidents/01M6FXDDGQRWHMYYWXY2...