SMapi Status

Up-to-date status of the SERPmetrics API. Visit @SERPmetrics for app & company updates.

[SMapi Status @smapistatus]

We're currently investigating an issue impacting both Bing and Yahoo SERP collection.

[SMapi Status @smapistatus]

We're aware of issues with fulfilment for Yahoo jobs today and are investigating the root cause.

[SMapi Status @smapistatus]

AWS us-east-1 is currently down, which is impacting our service. AWS are aware of the issue and are working on a resolution.

[SMapi Status @smapistatus]

[UPDATE] The planned maintenance originally scheduled for today will now take place on Sat 02 October @ 19:00-23:00 UTC

[SMapi Status @smapistatus]

Scheduled Maintenance: Thu 30 September @ 19:00-23:00 UTC. The API will be unavailable during this window.

[SMapi Status @smapistatus]

This issue is now intermittent so may continue to impact fulfilment for the next few hours however our queues are now successfully draining. We're continuing to monitor closely.

[SMapi Status @smapistatus]

We're experiencing an extended fulfilment outage this morning due to an issue with an upstream transit vendor. This is currently out of our direct control but we're monitoring closely. The API remains in service.

[SMapi Status @smapistatus]

We're aware of some markup changes affecting around 8% of Google fulfilment today. Our team are working on the necessary extraction updates which will be deployed within the next 6-12 hours.

[SMapi Status @smapistatus]

We have ongoing fulfilment delays on all queues this morning due to the extended AWS outage affecting services within us-east-1. We're closely monitoring the situation.

[SMapi Status @smapistatus]

This issue is now resolved.

[SMapi Status @smapistatus]

We're currently experiencing an outage on our priority queue affecting all customers. Our engineers are investigating the cause.

[SMapi Status @smapistatus]

We're currently experiencing an outage on our priority queue affecting all customers. Our engineers are investigating the cause.

[SMapi Status @smapistatus]

The earlier 503 issue affecting some users is now resolved; we'll continue monitoring closely.

[SMapi Status @smapistatus]

We're investigating reports of 503s for some users on the /keywords/serp endpoint

[SMapi Status @smapistatus]

Compose managed to restore access around 00:30 UTC and we've been monitoring since this time. We've had a few periods of higher than normal latency but overall things appear to now be stable.

[SMapi Status @smapistatus]

Unfortunately IBM Compose have still not resolved the issue within their AWS US-East-1 cluster and one of our core DBs remains inaccessible. You can subscribe to the incident directly for immediate updates by visiting: https://t.co/X8GYkymx94

[SMapi Status @smapistatus]

From Compose: "We are continuing to work on a fix for this issue. Progress is being made. We'll post more updates as we have them. Thanks for your patience."

[SMapi Status @smapistatus]

From Compose: "We've been able to stabilise internal network traffic and are now looking at gradually bringing things back back online." Their ETA on full cluster recovery is "hours" but we hope this is a worst-case estimate.

[SMapi Status @smapistatus]

Our database host (IBM Compose) have confirmed a wide-spread outage within their AWS cluster and are working to bring all services back online. Unfortunately we're reliant on their engineers at this stage but will post updates as we receive them.

[SMapi Status @smapistatus]

We're investigating an issue currently affecting database connectivity in AWS US-East-1 that's causing inbound API requests to timeout

[SMapi Status @smapistatus]

The pending queues is now draining at optimal speed and we're working hard to reach maximum fulfilment between now and 00:00 UTC.