Skip to content
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

Open
drjraclarke opened this issue Mar 17, 2025 · 4 comments
Open

ensembl rest API down? #680

drjraclarke opened this issue Mar 17, 2025 · 4 comments

Comments

@drjraclarke
Copy link

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.

@tsuyoi
Copy link

tsuyoi commented Mar 17, 2025

@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.

@miller34
Copy link

I'm also experiencing this issue.

@miller34
Copy link

@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.

@sgiorgetti
Copy link
Contributor

Hello @drjraclarke @tsuyoi @miller34 - thanks for flagging this up.
We are currently experiencing issues with internal services working intermittently, and these may affect different REST endpoints.
We are actively working on this, and we believe we have found the problem, which - regrettably - will take a few more days to fix.
This said, the expectation is for the issues - from your perspective - to gradually fade away, as we patch our infrastructure.

Shall keep this issue open to allow convenient communication channel.
Please, do not be shy and keep complaining here, as it does help.

Thank you very much for your patience and for using our services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants