REST API is failing this morning

API Issues
1

We noticed the first errors this morning around 7:33am, mainly 502s from the filing history endpoint but now we’re getting 503s (as well as some 401s):

<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
</body>
</html>
2

confirmed also failing for me.
note: we’ve observed sporadic latency spikes throughout the past week, rather than it just suddenly breaking this morning

companieshouse3
companieshouse32164×865 66.6 KB

3

We had a filing history release this morning at 07:37hrs and this has broken filing history. We are working to regress the release and get this working again.

2 Likes
4

Also experiencing failures this morning with the filing history endpoint.

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>
5

Now, it’s mainly 504s as well as 502s:

<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
6

all fixed.
https://forum.aws.chdev.org/t/filing-history-is-broken/8288

7

yep, thanks for the update and letting us know when resolved :+1:

8

@MArkWilliams note: we are still seeing spikes of 30 second filing-history requests since the fix.

As with my earlier comment, these latency spikes were happening yesterday as well. Please let me know if you need more info (e.g. specific times, IDs)

EDIT: Apologies. I may be lying/wrong. Investigating if there’s our own layer that is causing the latency. Everything seems perfect when using curl from shell.

1 Like
9

We have identified the earlier issues and they are now resolved. Monitoring continues, and so far it has
confirmed the fix was successful.

10

We’ve seen filing items without a date today (and it’s still there) which should not be optional. Is this a bug related to today release as well?

{
            "transaction_id": "MzQzMDk5NDczMWFkaXF6a2N4",
            "resolutions": [
                {
                    "category": "change-of-name",
                    "description": "resolution-change-of-name",
                    "type": "RES15",
                    "subcategory": "resolution",
                    "description_values": {
                        "resolution_date": "2024-07-30"
                    }
                }
            ],
            "associated_filings": [
                {
                    "category": "change-of-name",
                    "date": "2024-08-02",
                    "description": "change-of-name-by-resolution",
                    "type": "NM01"
                }
            ],
            "pages": 3,
            "links": {
                "self": "/company/10785869/filing-history/MzQzMDk5NDczMWFkaXF6a2N4",
                "document_metadata": "https://document-api.company-information.service.gov.uk/document/vUHiYYQuAsOc8Z7kUT9e-yMc1in65zGC8SlkOlYHylI"
            }
        }
11

There could have been some missing data in the filing history stream. They are being looked at and will probably result in them having to be re-processed, updated and appear on the stream again.

12

We have seen these “502 Bad Gateway” errors during the last few days. About 20 requests per day have failed with that error. Is there still a known issue?