LiteLLM Proxy Daily Activity API Overcounts Totals in Non-UTC Timezones — Timezone Edge Bug

What this error means

LiteLLM /user/daily/activity overstates totals for single-day window in non-UTC timezones is a LiteLLM failure pattern reported for developers trying to fix litellm daily activity api timezone counting bug overstates totals. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Open issue on official repo. Bug confirmed in timezone edge case for daily activity aggregation. Affects billing and monitoring accuracy for LiteLLM proxy users in non-UTC regions.

Common causes

• The /user/daily/activity endpoint in LiteLLM proxy overstates usage totals when queried with a single-day window in non-UTC timezones. This affects billing accuracy and usage monitoring for teams using LiteLLM as an API gateway across different timezone regions.
• Open issue on official repo. Bug confirmed in timezone edge case for daily activity aggregation. Affects billing and monitoring accuracy for LiteLLM proxy users in non-UTC regions.

Quick fixes

1. Confirm the exact error signature matches LiteLLM /user/daily/activity overstates totals for single-day window in non-UTC timezones.
2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/BerriAI/litellm/issues/27780

Evidence note: Open issue on official repo. Bug confirmed in timezone edge case for daily activity aggregation. Affects billing and monitoring accuracy for LiteLLM proxy users in non-UTC regions.

Related errors

• LiteLLM usage tracking timezone issue
• LiteLLM proxy billing incorrect

FAQ

What should I check first?

Start with the exact LiteLLM /user/daily/activity overstates totals for single-day window in non-UTC timezones text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed LiteLLM workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without LiteLLM /user/daily/activity overstates totals for single-day window in non-UTC timezones.