Bodyguard incident
Inreased latency on text analysis due to translation
Resolved after 38 minutes, affecting Bodyguard API (Username Analysis API) and Bodyguard API (Text Analysis API), on November 6, 2026.
The corrupted node have been drained and translation and username pod recreated. Latencies are back to normal. We continue to monitor.
Affected components
Update timeline
- identified Nov 06, 2026, 08:30 PM UTC
We are seing an increased latency on the analyze text endpoint. A translation pod is in cause, rejecting most of the received requests.
- identified Nov 06, 2026, 08:32 PM UTC
A username pod shared on the same node have increased latency as well impacting username analysis
- monitoring Nov 06, 2026, 08:35 PM UTC
The corrupted node have been drained and translation and username pod recreated. Latencies are back to normal. We continue to monitor.
- resolved Nov 06, 2026, 09:01 PM UTC
Stabilized latencies.
Your product runs on more than Bodyguard
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