THIS IS A SCHEDULED EVENT Aug <var data-var='date'>25</var>, <var data-var='time'>15:00</var> - <var data-var='time'>17:00</var> UTC Aug <var data-var='date'>19</var>, <var data-var='time'>16:37</var> UTC Scheduled - On August 24 @8pm PST Sentry will be performing maintenance on our central control plane. The purpose of this maintenance is to ensure the ongoing scalability and resilience of Sentry’s underlying systems. We anticipate this maintenance to take no more than two hours. During this maintenance our users may experience slowness with API calls and integrations. This will NOT impact the ingestion of events into Sentry’s system. We have chosen this time as it is between our peak periods during North American and European business hours, and represents the trough in events being ingested into Sentry’s system. Sentry will continually monitor systems throughout the entirety of the maintenance.

Control Plane Database Maintenance

Aug <var data-var='date'>18</var>, <var data-var='time'>22:21</var> UTC Resolved - The problem has been resolved, all backlogs have cleared and everything is operational again. Aug <var data-var='date'>18</var>, <var data-var='time'>22:15</var> UTC Monitoring - We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed. Aug <var data-var='date'>18</var>, <var data-var='time'>21:56</var> UTC Identified - We have identified the cause and are working to determine a mitigation. This is only affecting US right now. Aug <var data-var='date'>18</var>, <var data-var='time'>21:42</var> UTC Investigating - We are currently investigating a delay in evaluating alerts in the US region.

Alert backlogs in US

Aug <var data-var='date'>13</var>, <var data-var='time'>22:27</var> UTC Resolved - All backlogs have been processed. Aug <var data-var='date'>13</var>, <var data-var='time'>22:13</var> UTC Update - We continue to make progress on the spans backlog with an estimated completion time of 15 minutes. Aug <var data-var='date'>13</var>, <var data-var='time'>21:22</var> UTC Update - We're continuing to make progress on the span ingestion backlog in US. Aug <var data-var='date'>13</var>, <var data-var='time'>20:32</var> UTC Update - We've recovered all ingestion latency in DE. In US, errors have processed their backlog and we continue to make progress on spans in US. Aug <var data-var='date'>13</var>, <var data-var='time'>19:53</var> UTC Update - The problematic change has been reverted and we're processing backlogs. Aug <var data-var='date'>13</var>, <var data-var='time'>19:34</var> UTC Monitoring - The problematic change has been reverted and we're processing backlogs. Aug <var data-var='date'>13</var>, <var data-var='time'>18:35</var> UTC Identified - We've identified the source of latency and are reverting that change. Aug <var data-var='date'>13</var>, <var data-var='time'>18:07</var> UTC Update - We are currently investigating ingestion delays for spans, transactions and alerts in DE and US Aug <var data-var='date'>13</var>, <var data-var='time'>17:59</var> UTC Update - We are currently investigating ingestion delays for spans and transactions in DE and US Aug <var data-var='date'>13</var>, <var data-var='time'>17:47</var> UTC Investigating - We are currently investigating ingestion delays for spans and transactions in DE

Span & Transaction ingestion delayed in DE

Aug <var data-var='date'>12</var>, <var data-var='time'>22:52</var> UTC Resolved - Backlogs have been processed Aug <var data-var='date'>12</var>, <var data-var='time'>22:43</var> UTC Identified - We've mitigated the source of ingestion latency and are processing the backlog. Aug <var data-var='date'>12</var>, <var data-var='time'>21:58</var> UTC Investigating - We are currently investigating error ingestion latency in US.

Error ingestion delays in US

Aug <var data-var='date'>12</var>, <var data-var='time'>14:48</var> UTC Resolved - The backlog has been processed Aug <var data-var='date'>12</var>, <var data-var='time'>14:21</var> UTC Monitoring - We're processing new events and alerts in realtime, and continue to process the tail of the backlog. Aug <var data-var='date'>12</var>, <var data-var='time'>13:28</var> UTC Identified - A fix has been made and the backlog is being processed. Aug <var data-var='date'>12</var>, <var data-var='time'>12:36</var> UTC Update - We've identified the root cause and are actively working on mitigation. Aug <var data-var='date'>12</var>, <var data-var='time'>11:45</var> UTC Investigating - We are actively investigating this issue.

Delayed Error ingestion in our US region

Aug <var data-var='date'>12</var>, <var data-var='time'>14:24</var> UTC Resolved - API performance has returned to expected levels. Aug <var data-var='date'>12</var>, <var data-var='time'>13:14</var> UTC Monitoring - API performance has returned to expected levels. We are continuing to monitor. Aug <var data-var='date'>12</var>, <var data-var='time'>12:58</var> UTC Investigating - We are currently investigating reports of API timeouts for the Sentry API in our US region.

Sentry API timeouts (US)

Aug <var data-var='date'> 7</var>, <var data-var='time'>17:08</var> UTC Resolved - The ingestion delay is resolved Aug <var data-var='date'> 7</var>, <var data-var='time'>16:48</var> UTC Monitoring - Ingestion latency for spans, crons, and logs is back to normal levels. Aug <var data-var='date'> 7</var>, <var data-var='time'>16:30</var> UTC Identified - We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour Aug <var data-var='date'> 7</var>, <var data-var='time'>16:21</var> UTC Investigating - We are currently investigating the issue

Spans, crons, logs ingestion delayed in US region

Aug <var data-var='date'> 6</var>, <var data-var='time'>11:21</var> UTC Resolved - We've processed all backlogged events and have fully recovered. Aug <var data-var='date'> 6</var>, <var data-var='time'>10:50</var> UTC Monitoring - We're processing new events in real time, and are working through a backlog of events now. Aug <var data-var='date'> 6</var>, <var data-var='time'>10:25</var> UTC Update - We've identified the issue causing delays in ingestion and have applied a fix. We'll update again when we return to real time processing. Aug <var data-var='date'> 6</var>, <var data-var='time'>09:55</var> UTC Update - We are still actively investigating this issue. Aug <var data-var='date'> 6</var>, <var data-var='time'>08:59</var> UTC Investigating - We are actively investigating this issue.

Jul <var data-var='date'>27</var>, <var data-var='time'>18:27</var> UTC Resolved - The backlog has been cleared and ingestion is back to normal. Jul <var data-var='date'>27</var>, <var data-var='time'>18:07</var> UTC Monitoring - We have resolved the incident and are monitoring our ingestion backlog. Jul <var data-var='date'>27</var>, <var data-var='time'>16:56</var> UTC Identified - We have identified the issue and error and profile ingestion is back up in US. Expect delays in ingestion and alerting for errors and profiles. Jul <var data-var='date'>27</var>, <var data-var='time'>16:23</var> UTC Investigating - We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.

Error and profile ingestion issues in US

Jul <var data-var='date'>21</var>, <var data-var='time'>14:14</var> UTC Resolved - We've burned through our spans backlog. Latency across span consumers are normal. Jul <var data-var='date'>21</var>, <var data-var='time'>13:55</var> UTC Update - We're still burning through our spans backlog Jul <var data-var='date'>21</var>, <var data-var='time'>13:04</var> UTC Monitoring - We've found and fixed the root cause and are burning through our spans backlog. Ingestion should be back to normal in around an hour. Jul <var data-var='date'>21</var>, <var data-var='time'>12:20</var> UTC Update - We are still actively investigating this issue Jul <var data-var='date'>21</var>, <var data-var='time'>11:26</var> UTC Update - We are still actively investigating this issue Jul <var data-var='date'>21</var>, <var data-var='time'>10:30</var> UTC Investigating - We are actively investigating this issue

Delayed ingestion on us region

Jul <var data-var='date'>20</var>, <var data-var='time'>16:57</var> UTC Resolved - We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types. Jul <var data-var='date'>20</var>, <var data-var='time'>16:09</var> UTC Update - We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog. Jul <var data-var='date'>20</var>, <var data-var='time'>14:50</var> UTC Update - The backlog on attachments in our EU region is fully burned, and latency is back to normal. While new error events are being processed with normal latency, we have a backlog of old error events that we are now burning through. Jul <var data-var='date'>20</var>, <var data-var='time'>14:30</var> UTC Monitoring - We have implemented a fix for our attachment ingestion issue in our EU region, and are monitoring while the backlog burns. We will update here when latency is back to normal. Jul <var data-var='date'>20</var>, <var data-var='time'>13:47</var> UTC Update - We have implemented a fix for errors and feedback ingestion in our EU region, and latency for those pipelines has returned to normal. We are still working on fixing our attachments ingestion pipeline in EU. Jul <var data-var='date'>20</var>, <var data-var='time'>13:19</var> UTC Update - We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix. Jul <var data-var='date'>20</var>, <var data-var='time'>12:24</var> UTC Update - We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix. Jul <var data-var='date'>20</var>, <var data-var='time'>12:10</var> UTC Update - We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix. Jul <var data-var='date'>20</var>, <var data-var='time'>11:41</var> UTC Identified - We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are working on a fix. Jul <var data-var='date'>20</var>, <var data-var='time'>11:11</var> UTC Investigating - we are investigating an issue affecting errors ingestion in the DE/EU region

EU Region Error, Attachment, and Feedback latency

Jul <var data-var='date'>17</var>, <var data-var='time'>06:57</var> UTC Resolved - The webhook backlog is now resolved. Jul <var data-var='date'>17</var>, <var data-var='time'>05:49</var> UTC Update - The webhook backlog is processing. Jul <var data-var='date'>17</var>, <var data-var='time'>04:50</var> UTC Update - The webhook backlog is processing. Jul <var data-var='date'>17</var>, <var data-var='time'>03:49</var> UTC Update - The webhook backlog is processing. Estimated recovery is now 2-2.5 hours. Jul <var data-var='date'>17</var>, <var data-var='time'>02:44</var> UTC Update - The webhook backlog is processing. Jul <var data-var='date'>17</var>, <var data-var='time'>01:28</var> UTC Update - The webhook backlog is processing. Jul <var data-var='date'>17</var>, <var data-var='time'>00:44</var> UTC Update - The webhook backlog is being processed, ETA ~3 hours until fully caught up. Seer code reviews will run and linked Github issues and PRs will update incrementally. Jul <var data-var='date'>16</var>, <var data-var='time'>21:06</var> UTC Identified - The issue is mitigated and the webhook backlog is being processed. Seer code reviews will run and linked Github issues and PRs will update incrementally.

Github Integration Webhook processing delay

Jul <var data-var='date'>14</var>, <var data-var='time'>19:32</var> UTC Resolved - Feedback ingestion is back to realtime and the backlog has been processed. Jul <var data-var='date'>14</var>, <var data-var='time'>18:16</var> UTC Update - We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion. Jul <var data-var='date'>14</var>, <var data-var='time'>17:40</var> UTC Monitoring - We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion. Jul <var data-var='date'>14</var>, <var data-var='time'>17:02</var> UTC Update - We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. We are working to start allowing user feedback in DE. Jul <var data-var='date'>14</var>, <var data-var='time'>16:49</var> UTC Update - We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. Jul <var data-var='date'>14</var>, <var data-var='time'>16:42</var> UTC Identified - We have identified the problem and are working on recovery. Jul <var data-var='date'>14</var>, <var data-var='time'>15:42</var> UTC Update - We continue to investigate the issue. Jul <var data-var='date'>14</var>, <var data-var='time'>14:44</var> UTC Investigating - We are currently investigating the issue.

Error ingestion degraded in DE region

Jul <var data-var='date'>13</var>, <var data-var='time'>14:25</var> UTC Resolved - Service has been restored. Jul <var data-var='date'>13</var>, <var data-var='time'>12:41</var> UTC Monitoring - Service has been restored and we are actively monitoring the situation Jul <var data-var='date'>13</var>, <var data-var='time'>12:24</var> UTC Identified - We identified the issue and restoring service. Jul <var data-var='date'>13</var>, <var data-var='time'>11:51</var> UTC Investigating - We are investigating ingestion delays.

Ingestion delays in US

Jul <var data-var='date'>13</var>, <var data-var='time'>02:56</var> UTC Resolved - Ingestion has caught up and alerts have been restored. Jul <var data-var='date'>13</var>, <var data-var='time'>02:01</var> UTC Monitoring - We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately. Jul <var data-var='date'>13</var>, <var data-var='time'>01:46</var> UTC Identified - We have identified the problem and are working to restore ingestion Jul <var data-var='date'>13</var>, <var data-var='time'>00:58</var> UTC Investigating - We are currently investigating the issue.

Ingestion delayed for spans, logs, crons in US region

Jul <var data-var='date'>11</var>, <var data-var='time'>03:34</var> UTC Resolved - We have processed the backlog. Jul <var data-var='date'>11</var>, <var data-var='time'>03:28</var> UTC Monitoring - We have processed the majority of our backlog. We are now recovering the tail of the backlog. Jul <var data-var='date'>11</var>, <var data-var='time'>02:37</var> UTC Update - We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours Jul <var data-var='date'>11</var>, <var data-var='time'>01:46</var> UTC Update - We expect recovery of historical data to be complete within the next 2 hours. Jul <var data-var='date'>11</var>, <var data-var='time'>00:56</var> UTC Update - We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. Jul <var data-var='date'>11</var>, <var data-var='time'>00:04</var> UTC Update - We have identified the problem and are working on recovery. New errors are being processed in real time and we are in the process of consuming backlogged errors. Jul <var data-var='date'>10</var>, <var data-var='time'>23:02</var> UTC Identified - We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place. Jul <var data-var='date'>10</var>, <var data-var='time'>22:43</var> UTC Investigating - We are currently investigating this issue.

Error ingestion degraded in US region

Jul <var data-var='date'> 7</var>, <var data-var='time'>14:36</var> UTC Resolved - Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics. The configuration change is now reverted and the issue is fixed. Jul <var data-var='date'> 7</var>, <var data-var='time'>08:49</var> UTC Investigating - We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day

Incoherent number of processed logs

Jul <var data-var='date'> 7</var>, <var data-var='time'>00:55</var> UTC Resolved - The backlgo has been consumed and ingestion and alerting has returned to normal operation Jul <var data-var='date'> 6</var>, <var data-var='time'>23:55</var> UTC Update - We're continuing to burn down the EU spans, logs, and metrics ingestion backlog. Jul <var data-var='date'> 6</var>, <var data-var='time'>23:00</var> UTC Update - We are now processing the backlog in EU. Expect delays in ingestion and alerting for spans, logs, and metrics on the order of hours. We will keep this page updated as we make progress. Jul <var data-var='date'> 6</var>, <var data-var='time'>21:56</var> UTC Monitoring - API and dashboards for traces, logs, spans should be restored. Ingestion is still behind but is expected to catch up in the next few hours

DE items ingestion delayed

Jul <var data-var='date'> 6</var>, <var data-var='time'>22:18</var> UTC Resolved - US ingestion is back to normal. EU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3 Jul <var data-var='date'> 6</var>, <var data-var='time'>21:28</var> UTC Update - We're still burning the last of our backlog in US and expect to be back to normal the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident. Jul <var data-var='date'> 6</var>, <var data-var='time'>20:29</var> UTC Update - We're continuing burning our backlog in US and expect to be have it fully consumed within the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident. Jul <var data-var='date'> 6</var>, <var data-var='time'>19:26</var> UTC Update - We're continuing burning our backlog in US and expect to be have it fully consumed in about 1 hour. We're continuing to investigate the delayed ingestion in our EU region. Jul <var data-var='date'> 6</var>, <var data-var='time'>18:30</var> UTC Monitoring - We've taken steps to mitigate the issue in the US and we're burning our backlog and expect to be have it fully consumed in about 4 hours. We're continuing to investigate the delayed ingestion in our EU region. Jul <var data-var='date'> 6</var>, <var data-var='time'>17:14</var> UTC Update - We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions. Jul <var data-var='date'> 6</var>, <var data-var='time'>16:18</var> UTC Update - We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions. Jul <var data-var='date'> 6</var>, <var data-var='time'>15:22</var> UTC Update - We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions. Jul <var data-var='date'> 6</var>, <var data-var='time'>14:26</var> UTC Update - We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions. Jul <var data-var='date'> 6</var>, <var data-var='time'>13:30</var> UTC Investigating - We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions. Jul <var data-var='date'> 6</var>, <var data-var='time'>05:48</var> UTC Update - We're still consuming the backlog and monitoring the situation. Jul <var data-var='date'> 6</var>, <var data-var='time'>02:07</var> UTC Update - Backlog is being consumed and we’re still monitoring recovery Jul <var data-var='date'> 6</var>, <var data-var='time'>00:44</var> UTC Monitoring - The issue was fixed and we are now monitoring the fix Jul <var data-var='date'> 6</var>, <var data-var='time'>00:35</var> UTC Investigating - We are investigating consumers for spans, logs and metrics are not ingested

Spans, logs and metrics ingestion stopped

Jul <var data-var='date'> 2</var>, <var data-var='time'>03:56</var> UTC Resolved - All operations are back to normal, as of ~7:30PM PT Jul <var data-var='date'> 2</var>, <var data-var='time'>00:46</var> UTC Monitoring - The migration has been reversed in EU and US. Application functionality is restored but there is a 45 minute delay in ingestion in the US and no delay in EU Jul <var data-var='date'> 2</var>, <var data-var='time'>00:34</var> UTC Identified - We have identified a migration as the cause of the issue. We have reverted the migration in EU and are working on doing so in the US Jul <var data-var='date'> 2</var>, <var data-var='time'>00:17</var> UTC Investigating - We are currently investigating the issue.

Traces, spans, logs inaccesible for query or ingestion in de and us

Jul <var data-var='date'> 1</var>, <var data-var='time'>10:00</var> UTC Resolved - Data is now processed live and the system are fully operational. Jul <var data-var='date'> 1</var>, <var data-var='time'>06:14</var> UTC Update - We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested). Jul <var data-var='date'> 1</var>, <var data-var='time'>05:22</var> UTC Update - We continue to monitor the situation Jul <var data-var='date'> 1</var>, <var data-var='time'>04:26</var> UTC Update - We continue to monitor the situation Jul <var data-var='date'> 1</var>, <var data-var='time'>03:30</var> UTC Monitoring - We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01. Jul <var data-var='date'> 1</var>, <var data-var='time'>02:25</var> UTC Update - We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US Jul <var data-var='date'> 1</var>, <var data-var='time'>01:29</var> UTC Update - Our ingestion fix was not successful. We are continuing to investigate possible solutions Jul <var data-var='date'> 1</var>, <var data-var='time'>00:27</var> UTC Update - Our database is stabilized. We are attempting a fix to increase the ingestion rate. Jun <var data-var='date'>30</var>, <var data-var='time'>23:31</var> UTC Update - We continue to investigate the issue. Jun <var data-var='date'>30</var>, <var data-var='time'>22:50</var> UTC Update - We continue to investigate the issue Jun <var data-var='date'>30</var>, <var data-var='time'>21:42</var> UTC Update - We continue to investigate the issue. Ingestion delays are around 40 minutes now. Jun <var data-var='date'>30</var>, <var data-var='time'>21:16</var> UTC Investigating - We are currently investigating the issue

Ingestion and query issues for logs, spans, traces in US

Jun <var data-var='date'>24</var>, <var data-var='time'>20:48</var> UTC Resolved - The issue in our US region has been resolved, and ingestion latency is back to normal. Jun <var data-var='date'>24</var>, <var data-var='time'>19:53</var> UTC Monitoring - We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses. Jun <var data-var='date'>24</var>, <var data-var='time'>18:52</var> UTC Identified - We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.

Delayed Span ingestion, Replay ingestion, and Issue creation in our US region

Jun <var data-var='date'>12</var>, <var data-var='time'>11:30</var> UTC Resolved - From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the "Stats" in the organization settings. The data loss is purely informational without impact on billing or ingested data.

Missing SDK Client Reports and Rate Limiting Outcomes

Jun <var data-var='date'>11</var>, <var data-var='time'>14:48</var> UTC Resolved - This issue has been resolved. Jun <var data-var='date'>11</var>, <var data-var='time'>14:18</var> UTC Update - The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur. Jun <var data-var='date'>11</var>, <var data-var='time'>13:23</var> UTC Update - We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2. Since around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially degraded in the EU region. Jun <var data-var='date'>11</var>, <var data-var='time'>13:13</var> UTC Monitoring - Notifications delivery is now close to fully functional in US and DE. We have identified the root cause as caused by one of our cloud providers, and are closely monitoring the situation. Jun <var data-var='date'>11</var>, <var data-var='time'>11:51</var> UTC Update - We are continuing to investigate the degraded notifications. Jun <var data-var='date'>11</var>, <var data-var='time'>10:53</var> UTC Update - We are continuing to investigate the degraded notifications. Jun <var data-var='date'>11</var>, <var data-var='time'>09:50</var> UTC Investigating - We're currently investigating degraded notification delivery.

Notification delivery

Jun <var data-var='date'>10</var>, <var data-var='time'>10:28</var> UTC Resolved - Our auth systems are back operational Jun <var data-var='date'>10</var>, <var data-var='time'>10:17</var> UTC Update - We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems Jun <var data-var='date'>10</var>, <var data-var='time'>10:15</var> UTC Monitoring - We deployed a fix and are monitoring the situation. Jun <var data-var='date'>10</var>, <var data-var='time'>10:05</var> UTC Investigating - We are currently investigating the issue.

Is Sentry down?

Sentry status is UP

Lastest published events

Alert backlogs in US

Span & Transaction ingestion delayed in DE

Error ingestion delays in US

Sentry Services, Components and Regions

Recent Sentry events

Control Plane Database Maintenance

Alert backlogs in US

Span & Transaction ingestion delayed in DE

Error ingestion delays in US

Delayed Error ingestion in our US region

Sentry API timeouts (US)