GPT-6 Astra weekly usage suddenly burning ~5x faster after paid $80 reset

Summary

I am on ChatGPT Pro and have been using GPT-6 Astra heavily for weeks on the same ongoing build/workflow. My weekly Codex allowance is suddenly being consumed at roughly 5x my normal rate.

I also just purchased an $80 paid weekly reset, so this appears to be affecting a freshly reset paid allowance.

Normal baseline

• Model: GPT-6 Astra
• Same ongoing build / similar workload
• Heavy Astra usage for weeks
• Historically, 20% of weekly usage lasts 10+ hours for this workload

Current behavior

• Purchased an $80 weekly reset
• After the reset, approximately 20% of weekly usage was consumed in about 2 hours
• This is roughly a 5x increase in quota consumption compared with my established baseline
• There has been no comparable 5x increase in workload or change to the build that would explain the difference

Why this appears abnormal

This is not a comparison between Astra and another model. I am comparing Astra to my own prior Astra usage over multiple weeks, using the same build and similar working pattern.

There are also other recent reports involving unexpected Codex usage/reset behavior and unusually fast Astra quota consumption, including reports around paid/reset weekly limits.

Expected behavior

A freshly purchased weekly reset should provide the normal weekly allowance, and the same Astra workload should consume quota at approximately the same rate as it has over prior weeks.

Actual behavior

The newly reset weekly allowance is currently draining approximately 5x faster than my established Astra baseline.

Please investigate the server-side usage accounting for GPT-6 Astra and paid weekly resets, including whether recent rate-limit/metering changes or reset-accounting issues are causing excess weekly allowance consumption.

The report names no repository file, test, or entry point and asks for server-side investigation of GPT-6 Astra and paid weekly resets. Start by confirming whether Codex contains the relevant metering or reset code; otherwise route it to the service owner and compare reset consumption with prior Astra usage. Done means identifying and correcting the accounting discrepancy, with regression coverage if repository code is involved.