docs(blog): add July 21 progress updates to the Bedrock Invoke caching incident report - #628
Merged
Merged
Conversation
…g incident report
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 0d9e0ce. Configure here.
…g incident report
Contributor
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit f99cc48. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the incident report with the progress shipped since it was published. The Known limitations item about Vertex AI and Azure is resolved: litellm#33807 (merged July 20) applies the same model-aware mid-conversation system handling as Bedrock Invoke on both paths, verified live, with e2e coverage. The weekly automated load test action is done: litellm#34166 (merged July 21) runs concurrent multi-turn sessions weekly against real Anthropic and Bedrock Invoke and fails on anomalies in error rate, warm-turn cache read share, cache writes, p95 turn latency, or recorded spend. The e2e action is marked partially done: the live-Bedrock cache regression tests from litellm#32963 and litellm#33807 are merged, while the full 250k-token scripted Claude Code session remains in progress and keeps its in-progress wording
Note
Low Risk
Documentation-only edits to an existing blog post; no runtime or API behavior changes.
Overview
Adds July 21 status notes to the Bedrock Invoke prompt-caching incident post so follow-up work is visible without rewriting the original commitments.
Under What we are changing, the e2e bullet now records that live cache-regression tests from #32963 (Bedrock) and #33807 (Vertex AI and Azure) are merged, while the full ~250k-token Claude Code session remains in progress. The weekly load-test bullet is marked done via #34166: CI runs concurrent Claude Code-shaped sessions weekly against real Anthropic and Bedrock Invoke and fails on baseline drift in errors, warm-turn cache reads, cache writes, p95 latency, or spend.
Under Known limitations, item 2 gets an update that Vertex AI and Azure needed the same model-aware mid-conversation system handling as Bedrock Invoke; #33807 ships that behavior with live verification and e2e coverage, resolving that open question.
Reviewed by Cursor Bugbot for commit f99cc48. Bugbot is set up for automated code reviews on this repo. Configure here.