companies

matt_earl 2017-11-14 10:18:19 UTC #1

We're seeing regular 502 Bad Gateway errors on the /search/companies endpoint (we were seeing it yesterday too). Do you have any idea what is wrong and if it can be fixed?

dominique 2017-11-14 10:22:14 UTC #2

We also noticed the same 502 bad gateway error but I just tried again and it seems to be resolved.

Looks like a momentary hiccup

matt_earl 2017-11-14 10:45:21 UTC #3

OK, but there have been a few periodic "hiccups" over the last couple of weeks at least, each of which will negatively impact our business in a reasonably significant way while it is in effect. It would be good to know if the underlying issue has been found and when it might be fixed.

MArkWilliams 2017-11-14 11:00:13 UTC #4

we just had a problem with our new search servers, but it it resolved now.

matt_earl 2017-11-14 11:11:50 UTC #5

Great, thanks for the update Mark. We'll let you know if this starts happening again.

matt_earl 2018-01-03 12:03:03 UTC #6

We're getting this consistently again this morning (for the past 90 minutes at least). Can you take a look?

SimonMoorcroft 2018-01-03 12:06:23 UTC #7

We are seeing the same issue

MArkWilliams 2018-01-03 12:32:16 UTC #8

Apologies for the search service errors.
We had performance issues 10:30-10:51 and 11:20-12:01 caused by a small group of IP addresses hammering search.
Steps have been taken to resolve that and search is now back to normal.
Sorry for the inconvenience.

dickie 2018-01-05 11:36:30 UTC #9

Hi MArkWilliams, we think the problem returned yesterday morning after running tests on a number of reported errors we've had. Are you able to confirm if there were performance issues then as well?

MArkWilliams 2018-01-05 12:13:15 UTC #10

The peak load on 4/1/2017 was between 09:56 - 10:04.
We have been in contact with one particular customer who caused this peak, and do not envisage another occurrence.
Sorry for the inconvenience.

dickie 2018-01-08 11:23:45 UTC #11

Thanks MArkWilliams, unfortunately though the problem seems to have returned.

MArkWilliams 2018-01-08 11:58:48 UTC #12

Sorry, we have a serious issue this morning since about 10:26.
We are currently still working to resolve this issue.

MArkWilliams 2018-01-08 12:35:01 UTC #13

All resolved now. Sorry for the inconvenience.

liam_flanagan 2018-01-08 15:57:01 UTC #14

We are also seeing the same issues this morning.

If there is any more information from our side that could be useful in investigating the issues please let us know.

matt_earl 2018-01-10 12:10:28 UTC #15

We've been seeing this again this morning from 10:50 (and still going now). Is there a longer term fix you can apply to stop this happening so frequently?

dickie 2018-01-18 10:50:22 UTC #16

Hi MArkWilliams, this is happening again this morning. This is becoming a regular occurrence. Are you able to advise if a longer term solution is close?

MArkWilliams 2018-01-18 12:01:46 UTC #17

Yes there was an issue from 10:21 to 11:29.
This is the first this week.
All resolved now. Sorry for the inconvenience.
We are currently testing a number of changes/fixes to prevent these issues happening in the future.

dominique 2018-01-29 12:16:36 UTC #18

Happened again on 2018-01-29T12:02:47.175Z

Just saw this issue happening right now

MArkWilliams 2018-01-29 13:39:49 UTC #19

Yes, we did have issues between 11:40 - 12:01.
Sorry for any inconvenience.

dickie 2018-02-06 11:25:05 UTC #20

Here we go again. MArkWilliams, this is becoming a frequent occurrence. Please can you advise if a longer term fix is close?