Hi Ben,

All of these quota warnings are related to your use bandwidth quota.

Since you had consumed your bandwidth quota, secure bandwidth and URLFetch
where both unavailable since these necessarily use bandwidth quota.

Somewhat currently confusingly, bandwidth quota was listed as 'Okay' because
it had been entirely consumed, and so everything was being denied.  We are
re-working the 'rate' messaging to clarify the current status, as well as
working on updating our documentation so that the relationships between
quota are clear.

Also, please follow up or file a quota request for additional bandwidth if
you are consistently using your quota.

Please let me know if you have any questions.

Thanks,
Marzia

On Tue, Dec 16, 2008 at 10:42 PM, Ben Nevile <ben.nev...@gmail.com> wrote:

>
> I should also mention that when I last checked the dashboard at about
> 7-7:30pm PST the outgoing bandwidth was at 56%.
>
> Ben
>
>
>
> On Dec 16, 10:40 pm, Ben Nevile <ben.nev...@gmail.com> wrote:
> > the new quota details dashboard looks very nice.  thanks for your hard
> > work on this mr. and ms. googs.
> >
> > but hey, how come i've never had a problem with outgoing bandwidth
> > before, and tonight my app is stuck in the red zone?  the graph beside
> > "outgoing bandwidth" is in the red (10.00 of 10.00 GBytes) but the
> > rate is "okay", whereas the Secure Outgoing Bandwidth graph is at
> > zero, yet the rate is "high".  There's also a "high" rate for
> > UrlFetch's Data Sent to API, but I don't use UrlFetch.
> >
> > sigh. pissed off users again for me.
> > Ben
> >
> > ps. app is "n3xt"
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to