Dec 31, 2010 1000 Service responsive and current data returning
Adjustments to the datastore usage has stabilized service. Search results are becoming current and expected to be fully caught up by 1600 today.
Topsy Ops
Adjustments to the datastore usage has stabilized service. Search results are becoming current and expected to be fully caught up by 1600 today.
Topsy Ops
A datastore failure led to a service interruption. Recovery of the datastore restored port-level services. Data is not yet current and is expected to become current by noon today.
Topsy Ops
The service has remained stable since actions taken at 1100 today. All data input systems have been restored and current data should start appearing. The root causes has been tracked to a corrupted datastore which was locking up on specific data inserts. Repair of this corruption is underway as well, while a workaround is in place to prevent the service interruptions.
Topsy Ops
Port availability has been restored. Work is underway to get current data. Work is underway to prevent a failed datastore from causing service availability issues, and to determine the root cause of the datastore failure.
Topsy Ops
Topsy services have been intermittently up and down periodically over the past day. Working first to achieve port-level stability, then current data.
Topsy Ops
Streamsense service was interrupted during a routine maintenance activity. Investigation is ongoing into the unexpected dependency which led to the service interruption.
Topsy Ops
There was a brief service interruption during an emergency maintenance operation to restore a datastore server.
Topsy Ops
All services have been restored. The root cause was a system restart on a data store which should have been gracefully recovered from the web front end. Corrective action underway for graceful recovery. Diagnostic activity underway on system.
Topsy Ops
A service interruption is underway. The service is port-responsive but not returning search results.
Topsy Ops
A brief service outage occurred in the manner as occurred earlier today. Reconfiguration has been completed in order to address the immediate issue.
Topsy Ops