PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Sentry is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Sentry. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Sentry issues today?

As of Oct 12, 2026 20:15 UTC, 0 users had reported issues with Sentry in the previous 24 hours.

How can I report a Sentry outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is Sentry down right now?

NormalOfficial status last polled Oct 12, 2026 20:11 UTCsentry.io Official status page

Sentry error tracking

Are you on the Sentry team and see something inaccurate? Report it to us. We respond within one business day.

Is Sentry down right now?

No. Sentry has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 20:15 UTC

Normal

Sentry is operating normally

As of Oct 12, 2026 20:15 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 18, 2026 13:32 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Sentry.

Incident days

No recorded incident

4h 50m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Sentry. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

4h 50m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Sentry outage on September 18 4h 49m disruption

Sep 18, 08:42 AM → Sep 18, 01:32 PM · 4h 49m · high

A high-severity incident affected the Sentry service. This disruption was detected through automated signals, including the vendor's own status page. The incident began on September 18, 2026, and was resolved after approximately 4 hours and 49 minutes.

Duration

4h 49m

tracked by PulseWatch

Impact

During the 4-hour and 49-minute high-severity incident affecting the Sentry service, automated monitoring indicated a significant disruption. This incident was identified through vendor status page updates and synthetic probes. No user-reported data was collected for this incident, meaning there were no direct user reports, specific affected regions, or particular issue types recorded by our systems during this period.

Incident timeline

Sep 18, 08:42 AM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 18, 08:42 AM
Status updated: possible issue
Sep 18, 01:32 PM
Signals cleared — incident resolved

Official updates

Sep 18, 08:42 AM
Sentry status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.33%

90-day uptime

99.0%

Calculated from Sentry's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Sentry: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Sentry or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 8:42:40 AM · 4h 49m

08:42 AM01:32 PM

Detection9/18/2026, 8:42:40 AM · 24d ago

Detected — high severity

ResolvedMedium