-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ensembl rest API down? #680
Comments
@sgiorgetti Still seeing almost universal 502 status codes from both GRCh37 and GRCh38 REST endpoints. My understanding is any needed throttling will report a 429 error with the appropriate Retry-After header, but I'm not seeing that here, just 502 Bad Gateway status codes. |
I'm also experiencing this issue. |
@sgiorgetti It looks like some of the REST endpoints work consistently while others are intermittent. For instance, calling vep_region_get usually works unless other options are specified. Most of the boolean options also seem to work consistently, but I've had issues with dbNSFP, DosageSensitivity, GeneSplicer, tsl, per_gene, and mutfunc. It's very sporadic because sometimes the boolean flags will work, but they've been much more fickle over the past few days. |
Hello @drjraclarke @tsuyoi @miller34 - thanks for flagging this up. Shall keep this issue open to allow convenient communication channel. Thank you very much for your patience and for using our services. |
Hello. I am getting consistent 500 internal server errors when querying ensembl, with code that was working for weeks up until this morning. Is the server down? thank you very much.
The text was updated successfully, but these errors were encountered: