rewindex

CompaniesSentryIncidents

Sentry: sentry.io returns 502

No impact listedStatus: resolvedStarted Resolved (54 min)1 updatestatus.sentry.io (opens in new tab)

Timeline of updates

  1. resolved

    A primary database failover caused a brief outage of the site, but no data was lost. The reverted deploy was coincidental to the failover, but it was not a contributing factor. All services should be functioning normally now.

From Sentry’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.sentry.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Sentry, started 2024-02-12 20:14 UTC, resolved after 54 min, 1 update(s).

Title
sentry.io returns 502
Vendor
Sentry
Date
URL
https://rewindex.com/company/sentry/incidents/d2jqxbqt28pd

Sentry profileRecent Sentry incidentsAll outages on February 12, 2024Sentry in February 2024MarkdownJSON