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
May 22, 2015

No incidents reported today.

May 21, 2015

No incidents reported.

May 20, 2015
Postmortem - Read details
May 21, 08:07 UTC
Resolved - This incident has been resolved.
May 20, 22:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 18, 16:00 UTC
Update - Unfortunately a resolution to this issue is taking longer than expected. In the meantime, we recommend switching out your interaction.raw_content filters for a combination of the interaction.content, interaction.hashtags and interaction.mentions targets. Our team is still actively working on a resolution to this issue. We apologise for any inconvenience caused.
May 15, 20:54 UTC
Identified - We have identified an issue receiving interactions when filtering against the interaction.raw_content target
May 15, 17:28 UTC
Resolved - The maintenance was completed successfully.
May 20, 11:27 UTC
Monitoring - Users will experience delays in receiving data from push system between 2015-05-20 11:00 and 2015-05-20 11:15 UTC
May 20, 10:50 UTC
May 19, 2015

No incidents reported.

May 17, 2015

No incidents reported.

May 16, 2015

No incidents reported.

May 14, 2015

No incidents reported.

May 13, 2015

No incidents reported.

May 12, 2015

No incidents reported.

May 11, 2015

No incidents reported.

May 10, 2015
Resolved - This incident has been resolved.
May 10, 08:20 UTC
Monitoring - We're having an intermittent network issue. We believe it is resolved but will continue to monitor.
May 9, 19:49 UTC
Identified - The issue has been identified and a fix is being implemented.
May 9, 18:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 9, 18:48 UTC
Investigating - We are currently investigating this issue.
May 9, 18:42 UTC
May 8, 2015

No incidents reported.