DeepSeek V4 Peak Valley Pricing Change
21–30 of 37 posts
Re: DeepSeek V4 Peak Valley Pricing Change
#22Content restricted in the UK
Re: DeepSeek V4 Peak Valley Pricing Change
#23Earlier quoted context omitted.
> in California (PDT / UTC-7): 03:00 to 18:00, and 21:00 to 23:00. I think that’s incorrect. For California (PDT), 2X pricing will be in effect from 6–9pm and 11pm–3am. During PST, the CA windows will be 5–8pm and 10pm–2am.
> 2X pricing will be in effect from 6–9pm and 11pm–3am that's why cheaper price is 03-18 and 21-23, aka 3am-6pm,9pm-11pm
Re: DeepSeek V4 Peak Valley Pricing Change
#24Yall trust LLM providers sweeping up keys and passwords? Sometimes you have a little .env file or config files in your repos that are not checked in... LLMs like to read that stuff and send it in. I don't trust any of the LLM providers, but less so the ones seated in China.
Yes, never trust the perfidious chinamen or their evil LLMs. They are on another level of evil than our glorious and noble western LLMs that are used to bomb schools.
Re: DeepSeek V4 Peak Valley Pricing Change
#25So DeepSeek v4 will cost 2x between 9:00 to 12:00 and 14:00 to 18:00, Beijing Time. This is UTC+8 so to get cheaper DeepSeek: - in London (BST / UTC+1): 11:00 to 02:00, and 05:00 to 07:00. - in NY (EDT / UTC-4): 06:00 to 21:00, and 00:00 to 02:00. - in California (PDT / UTC-7): 03:00 to 18:00, and 21:00 to 23:00. Subscription plans like OpenCode Go might not even pass down this 2x cost since most customers are EU/US.
Note "cheaper" is only relative to the 2x peak price. The off-peak price is still the same price as today. In other words they hiked the price 2x for peak hours only.
Re: DeepSeek V4 Peak Valley Pricing Change
#26Re: DeepSeek V4 Peak Valley Pricing Change
#27Content restricted in the UK
Re: DeepSeek V4 Peak Valley Pricing Change
#28It's business at the end of the day. Don't get surprised if one day DeepSeek does a rug pull too.
Re: DeepSeek V4 Peak Valley Pricing Change
#29Re: DeepSeek V4 Peak Valley Pricing Change
#30Yall trust LLM providers sweeping up keys and passwords? Sometimes you have a little .env file or config files in your repos that are not checked in... LLMs like to read that stuff and send it in. I don't trust any of the LLM providers, but less so the ones seated in China.