Sentry incident

Ingestion IP addresses updates

Minor Resolved View vendor source →

Sentry experienced a minor incident on January 14, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 12:00 AM UTC
Resolved
Jan 14, 2026, 12:00 AM UTC
Duration
Detected by Pingoru
Jan 14, 2026, 12:00 AM UTC

Update timeline

  1. monitoring Jan 14, 2026, 12:00 AM UTC

    Jan 14, 00:00 UTC Completed - The scheduled maintenance has been completed. Jan 5, 16:55 UTC Update - We completed the brownout successfully. The involved DNS records are back to the previous addresses and the schedule for the final switch has been confirmed for Tuesday, January 13th, 08:00-19:00 UTC. Jan 5, 00:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 20, 09:35 UTC Scheduled - We're going to update the IP addresses of the following ingestion DNS records: - *.ingest.sentry.io (currently pointing to 34.120.195.249/32) - *.ingest.us.sentry.io (currently pointing to 34.120.195.249/32) - *.ingest.de.sentry.io (currently pointing to 34.120.62.213/32) to a new unified set of IPv4 and IPv6 addresses, specifically: - 34.160.81.0/32 - 34.102.210.18/32 - 2600:1901:0:5e8a::/64 - 2600:1901:0:7edb::/64 A brownout has been scheduled for Monday, January 5th, 15:30-16:00 UTC, where both the old IPs and the new ones will be used, on all DNS records: - *.ingest.sentry.io - *.ingest.de.sentry.io - *.ingest.us.sentry.io The switch has been scheduled for Tuesday, January 13th, 08:00-19:00 UTC on all DNS records: - *.ingest.sentry.io - *.ingest.de.sentry.io - *.ingest.us.sentry.io We advise customers to add the new IP addresses to any filtering/whitelisting policy setup in their network configuration.