Company Logo

Is there an Sift outage?

Sift status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for Sift and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Sift outages and incidents

Outage and incident data over the last 30 days for Sift.

There have been 0 outages or incidents for Sift in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Sift

Outlogger tracks the status of these components for Xero:

API Active
Console Active
Device Fingerprinting Active
Dispute Management Active
Dispute Real Time Resolution Active
Score Active
Workflows Active
Component Status
API Active
Console Active
Device Fingerprinting Active
Dispute Management Active
Dispute Real Time Resolution Active
Score Active
Workflows Active

Latest Sift outages and incidents.

View the latest incidents for Sift and check for official updates:

Updates:

  • Time: April 8, 2020, 4:19 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 8, 2020, 3:38 a.m.
    Status: Monitoring
    Update: All Sift systems are operational, but there is a backlog in event processing. We expect the queue to be completely processed in about 25 minutes.
  • Time: April 8, 2020, 3:28 a.m.
    Status: Investigating
    Update: We are currently investigating issues with our underlying cloud service provider. We are experiencing a partial failure of requests to our APIs at this time but will update as we assess impact further. Please contact [email protected] if you have any questions.

Updates:

  • Time: Jan. 14, 2020, 8:50 p.m.
    Status: Resolved
    Update: As of 12 noon PST the console back to normal load times. Please contact [email protected] if you are still noticing any issues.
  • Time: Jan. 14, 2020, 6:59 p.m.
    Status: Investigating
    Update: We're currently experiencing intermittent console slowness. We're investigating and working to resolve the issue as quickly as possible.

Updates:

  • Time: Dec. 23, 2019, 4:32 p.m.
    Status: Resolved
    Update: The issue has been resolved. Both logging in and our APIs are back to normal.
  • Time: Dec. 23, 2019, 4:13 p.m.
    Status: Investigating
    Update: We've received reports of users having difficulty logging in and intermittent increased latency on our APIs. We are currently investigating and working to identify and resolve the issue. If you have any questions, please email [email protected].

Updates:

  • Time: May 8, 2019, 2:34 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 8, 2019, 1:53 a.m.
    Status: Monitoring
    Update: The latencies have been reduced to normal ranges.
  • Time: May 8, 2019, 1:36 a.m.
    Status: Identified
    Update: The deployment of our fix is proceeding.
  • Time: May 8, 2019, 12:44 a.m.
    Status: Identified
    Update: Our fix is proceeding as planned. We continue to see elevated latencies to a small percentage scoring ATO requests, as well as asynchronous requests for non-ATO scores.
  • Time: May 7, 2019, 11:58 p.m.
    Status: Identified
    Update: We're proceeding with our fix for the issue.
  • Time: May 7, 2019, 11:18 p.m.
    Status: Identified
    Update: Fewer than 1% of ATO requests continue to see elevated latency. For non ATO products, synchronous requests latencies have returned to normal but we are still seeing elevated latency in a small percentage of asynchronous requests. So, a small percentage of non-ATO, asynchronous workflow runs are evaluating with a delay. We are deploying a fix to address these issues.
  • Time: May 7, 2019, 10:30 p.m.
    Status: Identified
    Update: We’ve isolated the issue and have made further progress in reducing elevated latencies. We’re working to completely fix the issue.
  • Time: May 7, 2019, 9:53 p.m.
    Status: Identified
    Update: We’ve made progress in reducing the percentage of calls with elevated latencies. We believe we have identified the issue and are working to get things fully back to normal. We noticed elevated latencies around 12:47pm Pacific Time, so you may have seen an increase in timeouts between then and now. Again, the vast majority of requests are being served at low latency and no data has been lost.
  • Time: May 7, 2019, 9:14 p.m.
    Status: Investigating
    Update: Ingestion of all events is operational and no data is being lost. The vast majority of all scoring continues to be done at low latencies. We are still seeing elevated scoring latencies in our synchronous and asynchronous scoring services for a small percentage of requests and are attempting to address.
  • Time: May 7, 2019, 8:36 p.m.
    Status: Investigating
    Update: We are currently experiencing elevated synchronous score API latencies and investigating the underlying problem.

Updates:

  • Time: April 5, 2019, 4:29 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 5, 2019, 4:27 a.m.
    Status: Monitoring
    Update: The backlog of events has been processed. All systems are healthy.
  • Time: April 5, 2019, 1:38 a.m.
    Status: Monitoring
    Update: The backlog of events have been processed and there is no more delay on asynchronous Scores and Workflows. There are delays to data in the Explore tab and we are currently working through the backlog of delayed messages.
  • Time: April 5, 2019, 1:11 a.m.
    Status: Monitoring
    Update: We are continuing to work through a small backlog of delayed events received through the Event API. Some updated scores, data in Explore, and workflows may be delayed by up to 2 hours after the event is received.
  • Time: April 5, 2019, 12:40 a.m.
    Status: Monitoring
    Update: We are continuing to work through a small backlog of delayed events received through the Event API. Some updated scores, data in Explore, and workflows may be delayed by up to 6 hours after the event is received.
  • Time: April 5, 2019, 12:09 a.m.
    Status: Monitoring
    Update: We are continuing to work through a small backlog of delayed events received through the Event API. Some updated scores, data in Explore, and workflows may be delayed by up to 6 hours after the event is received.
  • Time: April 4, 2019, 11:37 p.m.
    Status: Monitoring
    Update: We are continuing to work through a small backlog of delayed events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 6 hours after the event is received.
  • Time: April 4, 2019, 11:06 p.m.
    Status: Investigating
    Update: We are continuing to investigate a processing delay for a portion of events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 7 hours after the event is received. This does not impact events with synchronous scores or synchronous workflows. No data has been lost.
  • Time: April 4, 2019, 10:05 p.m.
    Status: Investigating
    Update: We are continuing to investigate a processing delay for a portion of events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 4 hours after the event is received. This does not impact events with synchronous scores or synchronous workflows. No data has been lost.
  • Time: April 4, 2019, 9:34 p.m.
    Status: Investigating
    Update: We are continuing to investigate a processing delay for a portion of events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 4 hours after the event is received. This does not impact events with synchronous scores or synchronous workflows. No data has been lost.
  • Time: April 4, 2019, 8:59 p.m.
    Status: Investigating
    Update: We are continuing to investigate a processing delay for a portion of events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 4 hours after the event is received. This does not impact events with synchronous scores or synchronous workflows. No data has been lost.
  • Time: April 4, 2019, 8:25 p.m.
    Status: Investigating
    Update: We are currently experiencing a processing delay for a portion of events received through the Event API. Updated scores, data in Explore, and workflows may be delayed by up to 4 hours after the event is received. This does not impact events with synchronous scores or synchronous workflows. No data has been lost.

Check the status of similar companies and alternatives to Sift

Qualys
Qualys

Systems Active

Ping Identity
Ping Identity

Systems Active

Veracode
Veracode

Systems Active

OPSWAT
OPSWAT

Systems Active

Sonatype
Sonatype

Systems Active

Aqua Security
Aqua Security

Systems Active

appviewx
appviewx

Systems Active

Signifyd
Signifyd

Systems Active

Alert Logic
Alert Logic

Systems Active

Red Canary
Red Canary

Systems Active

Frequently Asked Questions - Sift

Is there a Sift outage?
The current status of Sift is: Systems Active
Where can I find the official status page of Sift?
The official status page for Sift is here
How can I get notified if Sift is down or experiencing an outage?
To get notified of any status changes to Sift, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Sift every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Sift do?
Sift offers fraud prevention solutions to safeguard your business and customers, allowing for growth and innovation with minimal risk.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free