Timeline for What's going on with SEDE right now? It's being fickle
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 16 at 23:48 | comment | added | Aaron Bertrand Staff | @starball Some queries, yes, and a lot of other types of requests. I can't really disclose details, and precise timestamps are very cumbersome to pinpoint since the type of activity we're concerned about is usually ramped up very slowly. But I can tell exactly when one of the rule changes shut a huge portion of traffic down. :-) | |
Jan 16 at 22:40 | comment | added | starball | @AaronBertrand scraping as in actually running queries? for my curiosity, could you point to the datestamp under "queries -> everything" where those queries start being requested? | |
Jan 16 at 19:49 | comment | added | Aaron Bertrand Staff | I've definitely spotted high volumes of nefarious scraping-like activity from a handful of bots today, and will be working with SRE to tap some kneecaps. Not sure if it's related to the symptoms you've shared but I will resolve the current issue and then dig into similarities. | |
Jan 15 at 19:05 | comment | added | Stuck at 1337 | I'm seeing sluggishness now, but it's quite possible we've "meta effect"ed ourselves. It's still only a couple of web servers in front of a database so if everyone here is piling on, on top of who knows what kind of scraping and other stuff is happening... | |
Jan 15 at 18:26 | comment | added | Jesse |
@rene I don't think it's speed-related. I'm currently on a network with 400Mbps up and down and am encountering the same issue. Looking at the actual requests being sent, there's some weird behavior going on. After a handful of sub-second poll requests, the requests start taking multiple seconds each, and after about 4 or 5 I get "unknown job being polled". I've also randomly gotten the {"captcha":true} response while being logged in, which seems wrong. I've also gotten "A severe error occurred on the current command" a couple of times. The site, in general, is also just super slow.
|
|
Jan 15 at 8:40 | comment | added | starball | @rene that could be it... I was/am doing some stuff that's doing about 100ish KiB/s downstream and upstream. But now SEDE seems okay. | |
Jan 15 at 7:34 | comment | added | rene Mod | It seems client side network speed related. If I put Chrome on a throttle for 3G speed clicking the "Run Query" button returns me JSON instead of a rendered page. I've jet to encounter a server-side error but at least this gives me enough clues to get the JSON stuff fixed. | |
Jan 15 at 7:09 | comment | added | rene Mod | What @cocomac sees has been reported before meta.stackexchange.com/questions/354414/… but I hardly ever manage reproduce that. I can't repro here what the OP experieces. | |
Jan 15 at 3:22 | comment | added | cocomac |
I can reproduce SEDE issues. Trying to run a random query anonymously yields {"captcha":true} (a page containing just that). I'm also experiencing slow loading times on pages. Trying to log in gives this. I get a slightly-better, but still incomplete page with my userscripts and adblocker disabled. Refreshing a few times did get the login page eventually, though. /cc @AaronBertrand
|
|
Jan 15 at 0:53 | comment | added | Aaron Bertrand Staff | The last exception I see from the OpServer side for SEDE is on December 13th, and I've taken a few swings at things with no ill effects, so not sure what is happening to you... | |
Jan 14 at 23:20 | history | edited | starball | CC BY-SA 4.0 |
added 591 characters in body
|
Jan 14 at 23:10 | history | asked | starball | CC BY-SA 4.0 |