Does Sentry run uptime checks or host a status page?

No. Sentry surfaces the errors behind a degradation through search_issues and search_events and ties them to releases with find_releases, but it does not perform synthetic uptime checks or host a status page. Better Stack handles that side, so pair it with Sentry for detection plus diagnosis.

Why does Sentry rank first for uptime monitoring if it does not do uptime checks?

Because the high-value step is diagnosis. When uptime degrades, search_issues and search_events immediately surface the exceptions driving it and find_releases shows whether a deploy lines up. Detection from Better Stack or PagerDuty tells you something is down; Sentry tells you the code that is failing.

Sentry for uptime monitoring

Our top pick for uptime monitoringOfficialSentry712

Sentry's official server is the top pick in this uptime-monitoring lineup, and the reason is what happens after a degradation is detected. It lets an agent pull the error events, stack traces, and issue details behind a spike, so the question moves quickly from is something wrong to what is wrong and why.

It earns the lead here on diagnosis rather than detection: when uptime degrades, Sentry is where the exceptions driving it live, grouped and traced. The siblings handle the watching side, the synthetic checks and status pages, but Sentry answers the follow-up that actually matters, which broken code is causing the degradation.

How Sentry fits

search_issues surfaces the grouped problem behind a degradation and search_events queries the underlying events and replays for counts, so an agent reads the stack trace and sees how widespread the failure is. find_releases ties the spike to the release that introduced it, which often pinpoints what changed, and find_projects and find_organizations scope the search to the affected service.

The honest scope is important here: Sentry does not run synthetic uptime checks or host a status page, so it tells you what broke once something is degrading, not whether an endpoint is reachable from the outside. Better Stack is the stronger pick for actual uptime checks and status pages, Datadog for full observability across metrics, logs, and traces, and PagerDuty for paging the right responder when a service goes down. Sentry ranks first for the diagnostic half of uptime work; pair it with Better Stack so one watches the endpoint and the other explains the failure.

Tools you would use

Tool	What it does
whoami	Identifies the authenticated user in Sentry.
find_organizations	Finds organizations that the user has access to in Sentry.
find_teams	Finds teams in an organization in Sentry.
find_projects	Finds projects in Sentry.
find_releases	Finds releases in Sentry.
find_dsns	Lists all Sentry DSNs for a specific project.
create_team	Creates a new team in Sentry.
create_project	Creates a new project in Sentry (includes a DSN automatically).
update_project	Updates project settings such as name, slug, platform, and team assignment.
create_dsn	Creates an additional DSN for an existing project.

Full Sentry setup and config →

FAQ

Does Sentry run uptime checks or host a status page?: No. Sentry surfaces the errors behind a degradation through search_issues and search_events and ties them to releases with find_releases, but it does not perform synthetic uptime checks or host a status page. Better Stack handles that side, so pair it with Sentry for detection plus diagnosis.
Why does Sentry rank first for uptime monitoring if it does not do uptime checks?: Because the high-value step is diagnosis. When uptime degrades, search_issues and search_events immediately surface the exceptions driving it and find_releases shows whether a deploy lines up. Detection from Better Stack or PagerDuty tells you something is down; Sentry tells you the code that is failing.