# HubSpot's 37-Minute Lesson in Why HTTP 200 Can Lie

DevFeed: [HubSpot's 37-Minute Lesson in Why HTTP 200 Can Lie](<https://devfeed.tech/articles/hubspot-s-37-minute-lesson-in-why-http-200-can-lie-17936.md>)

Original publisher: [Read original article](<https://read.bytesizeddesign.com/p/hubspots-37-minute-lesson-in-why>)

Author: Byte-Sized Design

Published: 2026-04-22T16:34:15Z

Content type: article

Language: en

Sources: [Byte-Sized Design](<https://devfeed.tech/sources/byte-sized-design.md>)

Topics: [hubspot](<https://devfeed.tech/topics/hubspot.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [http](<https://devfeed.tech/tags/http.md>), [hubspot](<https://devfeed.tech/tags/hubspot.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [permission](<https://devfeed.tech/tags/permission.md>)

## AI overview

The article examines a HubSpot access incident in which a permission check passed while users were locked out, showing that an HTTP 200 response and conventional availability monitoring may not reflect whether users can actually access a service.

## Source excerpt

The permission check that passed, the users who were locked out, and what monitoring for "availability" actually misses