3 ms·
Service should be nearly restored at this point. We apologize for the significant interrupt to everyones days. As most of you all figured out at this point the
by zeeg 4y ago
Service should be nearly restored at this point. We apologize for the significant interrupt to everyones days. As most of you all figured out at this point the issue was with a regional failure in GCP (central, which is our primary zone). We're going to be exploring what we can do to lessen a single zone failure, and more importantly, reduce/remove any impact of the storage services being unavailable.
<3
- zeeg 4y agoFor folks reading this - and we'll solve this at a global scale - check your `SENTRY_DSN` setting and if its not using something like `oXXXXX.ingest.sentry.io` you should consider rolling out the updated value (located in your project settings). Our master domain routing layer is a more complicated failure point, and moving to the ingest based domains pushes you to our edge layer which _should_ be extremely reliable as well as much reduced global latency.