Error: Console request failed: endpoint is temporarily unavailable.
Just started getting this error:
Error: Console request failed: endpoint is temporarily unavailable. Check your quotas and/or contact our support.Is there an issue on Neon side?
12 Replies
conscious-sapphire•2y ago
Hey! I assume you're on the free tier and you're using branches, correct?
If that's the case then it means you consumed the monthly quota for compute hours
extended-salmonOP•2y ago
Yes, right. Looks like this is the case.
Would be nice if the error message pointed that out.
Just to make sure I use branches correctly, do I get it right that if I want to prototype an app and have a
dev branch for local development and main branch for production, then all I have for dev is 5 compute hours per month? 🤔extended-salmonOP•2y ago
The pricing page says 20 hours for branches, while the Usage on the Dashboard says only 5 hours.
extended-salmonOP•2y ago
Is there any way to see how my compute hours were spent so I could potentially optimize the spend?
conscious-sapphire•2y ago
Would be nice if the error message pointed that out.This is actually something we're actively working on
The pricing page says 20 hours for branches, while the Usage on the Dashboard says only 5 hours.This is another thing we're working on. There are two concepts when it comes to our billing: - Active hour: a measure of the amount of time a compute is active. The time your compute is idle when suspended due to inactivity is not counted. This is 20h - Compute hour: one active hour for a compute with 1 vCPU. For a compute with .25 vCPU (what's on the free tier), it takes 4 active hours to use 1 compute hour. On the other hand, if your compute has 4 vCPUs, it takes only 15 minutes to use 1 compute hour. That's why you see the "5 hours" Does that make sense? Feel free to share your feedback
extended-salmonOP•2y ago
Right, I see now.
I must say that while I understand that "20 hours of usage" looks better than the equivalent "5 hours of compute" on the free tier, it's also very confusing and even somewhat misleading since the other tiers show "compute hours".
When you say "we're working on this", could you shed some light on what sort of changes can we expect?
conscious-sapphire•2y ago
When you say "we're working on this", could you shed some light on what sort of changes can we expect?Clearer messaging in the UI and our landing page
I must say that while I understand that "20 hours of usage" looks better than the equivalent "5 hours of compute" on the free tier, it's also very confusing and even somewhat misleading since the other tiers show "compute hours".That's valid feedback
extended-salmonOP•2y ago
Do I understand correctly that on the free tier I can do 240 requests/month max?
My calculation is: 20 active hours * 60 min = 1200 active minutes
And, since every requests wastes at least 5 minutes of active time (which is the fixed autosuspend on the free tier), we get:
1200 active minutes / 5 minutes autosuspend = 240
conscious-sapphire•2y ago
So the branch used for production can run 24/7 throughout the month. If you're using branches for non-production workloads, you shouldn't be getting a ton of consistent traffic
extended-salmonOP•2y ago
I get that the production branch can run 24/7. This is great and very generous, thanks!
My question is about using a branch during development. I hope I'm missing something basic in my calculation, but am I wrong saying that I can do only 240 requests/month to a branch on a free tier? (it's like 8 requests per day, which feels very limiting)
conscious-sapphire•2y ago
Well, while a compute is active during the 5 minutes, you can make more than a single request 😄
extended-salmonOP•2y ago
right 🙂