Pro subscriber - service completely unusable, constant Internal Server Errors

Hi there,

Really sorry to hear you’ve been dealing with this it’s understandably frustrating, especially as a Pro subscriber expecting reliable access.

A few things to help clarify and (hopefully) move this forward:

1. Status page vs real-world issues The status page usually reflects system-wide outages , but it doesn’t always capture regional issues, account-specific problems, or partial service disruptions. So it’s possible for things to appear “operational” while some users (or regions like parts of the EU) are still experiencing errors.

2. Internal Server Errors during generation What you’re describing—failures mid-generation across multiple models—can sometimes be caused by:

• Temporary backend instability or load issues

• Region-specific routing problems

• Account/session-related glitches (especially after plan changes or renewals)

Since you’ve already tried different browsers and cleared cache, it likely isn’t a local issue on your end.

3. Quota being used on failed requests You’re right to flag this—failed generations shouldn’t meaningfully impact your usage. If they are, that’s something support definitely needs to review and potentially credit back.

4. What to do next (important) At this point, the best step is to contact official support directly with details so they can investigate your account:

Include:

• Approximate timestamps of failed requests

• Models you were using

• Screenshots or error messages (if possible)

• Confirmation that it’s happening across browsers/devices

This helps them trace logs and identify whether it’s a backend or account-specific issue.

5. On Pro plan expectations I understand your concern here. While Pro plans generally provide priority access and higher limits , they don’t guarantee zero downtime. That said, repeated failures like you’re describing especially over multiple days are not typical and should be addressed.