Page MenuHomePhabricator

Wikidata SPARQL query performance regression: frequent 502-bad gateway errors
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

  • Execute any SPARQL query either via the frontend (https://query.wikidata.org) or via the API-backend that wasn't cached previously. This can appears to affect any query, simple or complex.

What happens?:
Since 1 or 2 days (2026-05-07 or 2026-05-07) even very simple queries time out or get a bad gateway (HTTP 502) response.

What should have happened instead?:
Get a response without 502-error and no timeouts on simple queries.

Bildschirmfoto vom 2026-05-09 19-55-44.png (1,694×989 px, 105 KB)

Event Timeline

Nylki updated the task description. (Show Details)
Nylki renamed this task from Wikidata SPARQL query performance regression: frequent 502-errors and unusual timeouts to Wikidata SPARQL query performance regression: frequent 502-bad gateway errors.May 9 2026, 5:56 PM
Nylki updated the task description. (Show Details)

Still seeing IllegalArgumentException from out-of-range coordinates in wikibase:box queries. One relatively low-effort improvement might be validating coordinate bounds at the proxy layer before queries reach Blazegraph.

@HakanIST Hm, did you perhaps mean to comment in a different ticket? Not sure this is related. In fact I'd close this one, as the incident ( T425758 ) has been resolved.

@HakanIST Hm, did you perhaps mean to comment in a different ticket? Not sure this is related. In fact I'd close this one, as the incident ( T425758 ) has been resolved.

you're right, glad it's resolved

Nylki claimed this task.