API Search seems to be down - Getting 403 and 502

API Issues
#21

Working for us now too, thanks!

#22

All good now, thanks @MArkWilliams and team

#23

Thank you for the confirmation.
The network team have regressed part of the change that happened at 08:00hrs today.
They will continue investigations as to why this was not ‘foreseen’.
Thank you for your communications, they certainly helped us to identify the issue quickly.

#24

HI, the API is back, which is great but we still have a 403 error when trying to use the Companies House Search (https://find-and-update.company-information.service.gov.uk/).
We’re using virtual desktops on Azure so it might be because we’re part of a “cloud” IP.

#25

I’m still getting 403 errors on streaming API (companies & officers end points) at 10:22.
This is from a on premises server in Essex, not cloud.

#26

I too am still getting 403’s on the streaming API (from AWS London zone):

<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>

Working locally though.

#27

We have just (10:47hrs) made another ‘relaxation’ of some rules that will hopefully fix the last issues reported here.
If you are still having issues, please message here and I will DM you for IP address details that I can pass over to my network guys incase there is anything else.
I hope there will not be any more issues.

#28

Retried at 10:57AM and got a 403:

<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>

with headers:

  connection: 'keep-alive',
  'content-length': '118',
  'content-type': 'text/html',
  date: 'Wed, 08 May 2024 09:57:49 GMT',
  server: 'awselb/2.0'
#29

Mark we are getting 403’s as well - help appreciated.

#30

Still having streaming issues, happy to provide IP’s in DM.

Thanks

#31

The issue seemed fix and we were able to get successful responses again, but now the issue is back since the time you said another “relaxation” was made.

#32

If any help Mark - we can connect form the cloud and locally via Python but not .Net.
Have you guys maybe restricted access based on client ?

#33

…and just now (11:07hrs) another AWS ruleset has been taken off. Let me know if that is now fixed.

1 Like
#34

Not sure how long it takes to apply the change, but 2 minutes after I’m still getting 403s:

403
{
  connection: 'keep-alive',
  'content-length': '118',
  'content-type': 'text/html',
  date: 'Wed, 08 May 2024 10:08:52 GMT',
  server: 'awselb/2.0'
}
#35

All good now Mark - thanks for the prompt help!

1 Like
#36

All good now, thank you!

1 Like
#37

Can confirm, we are no longer seeing issues.

1 Like
#38

Working for me now, thanks. 200 response codes

1 Like
#39

Yes, now working for me too.

1 Like
#40

@MArkWilliams we have not settled back to OK responses.

(Colleague of @tiago.salgado 's)