Data center migration (primary DC switch)
Scheduled Maintenance Report for Twingly
Completed
The scheduled maintenance has been completed, everything works as expected at full capacity.
Posted Oct 17, 2018 - 17:48 CEST
Update
We are continuing to verify the maintenance items.
Posted Oct 17, 2018 - 16:58 CEST
Update
We are continuing to verify the maintenance items.
Posted Oct 17, 2018 - 16:27 CEST
Verifying
We have now completed the switch to our new data center (STH). The blog data collection has been resumed, and the system is ingesting the backlog.

Blog Search API and Blog LiveFeed API are being served from the new data center.
Posted Oct 17, 2018 - 13:52 CEST
Update
We will now pause our blog data collection. No new blog data will be collected for some time today. We will announce again when we resume the blog data collection.

We do not expect any data loss, i.e. missing posts, but after resuming the blog data collection there will some delays until the backlog has been consumed. During the day, there might be some downtime for the blog APIs.
Posted Oct 17, 2018 - 10:25 CEST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Oct 17, 2018 - 09:00 CEST
Scheduled
Our migration is going forward according to plan. During this maintenance window we will promote our new data center (STH) to be our primary DC.

To ensure consistency, all related services will be stopped during the switch, no new blog data will be collected during this time and there will be some downtime for the blog APIs. We do not expect any data loss, i.e. missing posts, but during the switch there will be a delay until we’ve consumed the backlog.

During the switch, the DNS record `api.twingly.com` will be updated, please ensure you respect the TTL for this record.

This work will not affect News, Social Feed or Forum data.

For an overview on our plan, please see: https://developer.twingly.com/2018/10/02/data-center-migration-plan/
Posted Oct 08, 2018 - 10:00 CEST
This scheduled maintenance affected: Blog Search API v3, Blog LiveFeed API v5, Data center STH, and Blog Data collection.