2027-03-27 Bad Request Status Code (400) for portion of traffic

Incident Report for Observe

Resolved

This incident has been resolved.
Posted Mar 27, 2025 - 20:54 PDT

Update

We are continuing to monitor for any further issues.
Posted Mar 27, 2025 - 19:50 PDT

Update

We are continuing to monitor for any further issues.
Posted Mar 27, 2025 - 19:50 PDT

Monitoring

We've identified an issue causing 400 Bad Request status code to be returned for a portion of traffic to the /v1/otel/v1/metrics ingest endpoint in the US East (N. Virginia) region. As a result, data points in this traffic were not being successfully ingested by Observe. Our team has identified and remediated the root cause, and this traffic is now successfully being ingested. The duration of the impact was approximately 1 hour 40 minutes.
Posted Mar 27, 2025 - 19:49 PDT
← Current Status Powered by Atlassian Statuspage