## Description

`/tag/daily/activity` endpoint occasionally returns spend values that are ~$25–$65 higher than the actual value for a few minutes, then returns to the correct value.

This causes budget management scripts (like ours) to incorrectly detect budget-exceeded and trigger provider failover logic unnecessarily.

## Behavior

- Spend for an active tag spikes temporarily by a fixed amount ($25–$65) - Returns to correct value 5–15 minutes later - Only the **currently-routed (active) provider tag** is affected — inactive tags remain stable - The spike amount correlates with the top 1-2 API keys' spend for the current day

## Environment

- LiteLLM Proxy: self-hosted - Backend: AWS Bedrock (via tag-based routing) - Script polling interval: 5 minutes via `/tag/daily/activity?page_size=100`

## Steps to Reproduce

1. Route traffic through a provider tag actively accumulating daily spend near its budget limit 2. Poll `/tag/daily/activity` every 5 minutes summing `metadata.total_spend` across pages 3. Observe: spend value spikes temporarily above the correct value, then normalizes

## Observed Values (example)

| Time | Reported spend | Expected spend | Spike | |-------|----------…