ops: note the standing 503 from /api/pro-monitor (pro path itself healthy) - #722
Merged
Conversation
… pro rewrite path is healthy Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018ePnwo4nBWCWvFvpy1YgCN
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Observed on 2026-09-04 across three production deployments (before and after the key rotation): the 15-minute
GET /api/pro-monitorreturns 503monitor_unavailableevery tick, while its synthetic proPOST /api/rewritereturns 200. Recorded under the existing open loop about the first healthy OBS receipt; owner to inspect the observability adapters.🤖 Generated with Claude Code
https://claude.ai/code/session_018ePnwo4nBWCWvFvpy1YgCN