Resolved on April 22, 2022.
A few hours ago, we deployed a change to our error capturing process to improve infrastructure performance. During the deployment, one of our services failed to come back online due to a locked file, but due to a gap in our instrumentation we failed to see the problem right away. You may see a small gap in your error data today while the service was locked. I regret the mistake and we are taking steps to improve our instrumentation and deployment process so that it does not happen again.
Update timeline
- resolved Apr 22, 2022, 08:49 PM UTC
A few hours ago, we deployed a change to our error capturing process to improve infrastructure performance. During the deployment, one of our services failed to come back online due to a locked file, but due to a gap in our instrumentation we failed to see the problem right away. You may see a small gap in your error data today while the service was locked. I regret the mistake and we are taking steps to improve our instrumentation and deployment process so that it does not happen again.
Your product runs on more than TrackJS
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services