All Systems Operational

About This Site

This website shows live status & latency information about the DataSift.com platform. Please check http://dev.datasift.com/issues/ for information on non-transient issues.

Frontend ? Operational
HTTP(s) Streaming ? Operational
Push System ? Operational
Filtering ? Operational
Augmentations ? Operational
Input Streams ? Operational
Historics ? Operational
Recordings Operational
Operational
Degraded Performance
Partial Outage
Major Outage
System Metrics Month Week Day
Interaction Delay Time
Fetching
Past Incidents
Apr 1, 2015

No incidents reported today.

Mar 31, 2015

No incidents reported.

Mar 30, 2015

No incidents reported.

Mar 29, 2015

No incidents reported.

Mar 28, 2015

No incidents reported.

Mar 27, 2015

No incidents reported.

Mar 26, 2015

No incidents reported.

Mar 25, 2015

No incidents reported.

Mar 24, 2015
Resolved - This incident has been resolved.
Mar 24, 20:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 24, 19:34 UTC
Update - Most features are now operational
Mar 24, 17:33 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 24, 16:51 UTC
Investigating - We have detected an issue resulting in lower than expected volumes of delivery. A separate but related issue is causing availability issues with the API.
Mar 24, 15:35 UTC
Mar 23, 2015

No incidents reported.

Mar 22, 2015

No incidents reported.

Mar 21, 2015

No incidents reported.

Mar 20, 2015

No incidents reported.

Mar 19, 2015
Resolved - This incident has been resolved.
Mar 19, 13:13 UTC
Update - Investigating issue with the datasift frontend
Mar 19, 12:51 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 19, 11:07 UTC
Investigating - We are currently investigating this issue.
Mar 19, 10:51 UTC
Mar 18, 2015
Resolved - Fix in place and Twitter firehose being received as normal
Mar 18, 20:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 18, 19:47 UTC
Identified - An issue has been identified with our ingestion of the Twitter firehose. We are investigating.
Mar 18, 17:41 UTC