Company Logo

Is there an SearchStax outage?

SearchStax status: Under Maintenance

Last checked: 6 minutes ago

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

Subscribe for updates

SearchStax outages and incidents

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

There have been 0 outages or incidents for SearchStax 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 SearchStax

Outlogger tracks the status of these components for Xero:

Component Status

Latest SearchStax outages and incidents.

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

Updates:

  • Time: April 17, 2021, 2:18 a.m.
    Status: Resolved
    Update: Our team has put a fix in place for the single node NDN deployments in Azure and the issue is now resolved.
  • Time: April 16, 2021, 7:40 p.m.
    Status: Identified
    Update: We have identified the issue to be localized to single-node deployments (NDN) in Azure. Our team is working on putting a fix in place.
  • Time: April 16, 2021, 4:54 p.m.
    Status: Investigating
    Update: We are observing some failures when creating new Solr Deployments. The failures are at this time random and our team is working to identify the reason.

Updates:

  • Time: April 2, 2021, 1:19 a.m.
    Status: Resolved
    Update: This incident has been marked as resolved. Impact of the Incident: * SearchStax Solr deployments were not impacted by this incident. * Since Pulse agents contact app.searchstax.com from the Azure nodes, they were impacted by the Azure DNS outage. As Pulse service did not receive any data from them over a time period, heartbeat alerts were reported.
  • Time: April 1, 2021, 10:58 p.m.
    Status: Monitoring
    Update: All existing heartbeat alerts have cleared out. Azure status page still reports Network Infrastructure Issues. Our team is closely monitoring the issue, but we do not see any ongoing issues with SearchStax deployments.
  • Time: April 1, 2021, 10:13 p.m.
    Status: Investigating
    Update: Our team has observed a high number of heartbeat alerts with Azure Deployments. Our initial investigation shows that this is because of issues with Azure DNS: https://status.azure.com/en-gb/status.

Updates:

  • Time: April 2, 2021, 1:19 a.m.
    Status: Resolved
    Update: This incident has been marked as resolved. Impact of the Incident: * SearchStax Solr deployments were not impacted by this incident. * Since Pulse agents contact app.searchstax.com from the Azure nodes, they were impacted by the Azure DNS outage. As Pulse service did not receive any data from them over a time period, heartbeat alerts were reported.
  • Time: April 1, 2021, 10:58 p.m.
    Status: Monitoring
    Update: All existing heartbeat alerts have cleared out. Azure status page still reports Network Infrastructure Issues. Our team is closely monitoring the issue, but we do not see any ongoing issues with SearchStax deployments.
  • Time: April 1, 2021, 10:13 p.m.
    Status: Investigating
    Update: Our team has observed a high number of heartbeat alerts with Azure Deployments. Our initial investigation shows that this is because of issues with Azure DNS: https://status.azure.com/en-gb/status.

Updates:

  • Time: March 16, 2021, 2:23 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 16, 2021, 2:23 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 15, 2021, 11:17 p.m.
    Status: Monitoring
    Update: Azure has rolled out a fix and all services are functional again. We will be closely monitoring the services for the next hour before we close the incident.
  • Time: March 15, 2021, 11:17 p.m.
    Status: Monitoring
    Update: Azure has rolled out a fix and all services are functional again. We will be closely monitoring the services for the next hour before we close the incident.
  • Time: March 15, 2021, 9:19 p.m.
    Status: Identified
    Update: Updated status from Azure: "CURRENT STATUS: Engineering teams are currently rolling out mitigation worldwide. Customers should begin seeing recovery at this time, with full mitigation expected within 60 minutes." You can also check the latest status on the Azure site here: https://status.azure.com/en-us/status
  • Time: March 15, 2021, 9:19 p.m.
    Status: Identified
    Update: Updated status from Azure: "CURRENT STATUS: Engineering teams are currently rolling out mitigation worldwide. Customers should begin seeing recovery at this time, with full mitigation expected within 60 minutes." You can also check the latest status on the Azure site here: https://status.azure.com/en-us/status
  • Time: March 15, 2021, 7:50 p.m.
    Status: Identified
    Update: Azure Status page is now reflecting the errors - https://status.azure.com/en-us/status "WarningAuthentication errors across multiple Microsoft services - Investigating SUMMARY OF IMPACT: Starting at approximately 19:15 UTC on 15 Mar 2021, a subset of customers may experience issues authenticating into Microsoft services, including the Azure Portal."
  • Time: March 15, 2021, 7:50 p.m.
    Status: Identified
    Update: Azure Status page is now reflecting the errors - https://status.azure.com/en-us/status "WarningAuthentication errors across multiple Microsoft services - Investigating SUMMARY OF IMPACT: Starting at approximately 19:15 UTC on 15 Mar 2021, a subset of customers may experience issues authenticating into Microsoft services, including the Azure Portal."
  • Time: March 15, 2021, 7:42 p.m.
    Status: Investigating
    Update: Our team has observed an increased error rate with Azure Management APIs. This affects provisioning new deployments in Azure, taking backups of Azure deployments and Total Requests metrics, and alert on Total Request for Azure deployments. Our team is investigating the issue.
  • Time: March 15, 2021, 7:42 p.m.
    Status: Investigating
    Update: Our team has observed an increased error rate with Azure Management APIs. This affects provisioning new deployments in Azure, taking backups of Azure deployments and Total Requests metrics, and alert on Total Request for Azure deployments. Our team is investigating the issue.

Updates:

  • Time: Feb. 6, 2021, 1:21 a.m.
    Status: Resolved
    Update: A bug was found in SearchStax’s Managed Solr alerting capability that related to Search & Indexing errors, where the service looked at the average number of errors across the Solr collections to determine the total number of errors, instead of summing them up. On Thursday, 4th February 2021, at 1:32pm UTC, a bug fix was released for Search & Indexing Threshold alert that fixed this bug, and now correctly sums the errors across all collections. What is the impact on you? Since the bug fix, you could be receiving more alerts for Search & Indexing errors. However, these are valid alerts and reflect the actual number of errors on the deployment. How are the Search Errors impacting you? One of the most common reasons for search errors is a malformed query, or querying on a field that doesn't exist. The logs will contain the detail about the query that needs to be fixed. Based on how your application handles this, it could be showing either an error message to the client, or not showing any results for those queries. How are the Indexing Errors impacting you? Schema mismatches are the most common reason for indexing errors. Your application could be trying to index a document containing a field that is not defined in the schema. In this case, Solr would not be indexing this document. This impacts the search on your application as the new document, or the updated contents of the old document will not be present in the search results. * If you are receiving these alerts, and would like us to find the reason, please feel free to reach out to SearchStax support. * If you are receiving these alerts, and know the reason, but need time to resolve the issues, and would like to not get the triggers, again and again, you can pause the alerts from the SearchStax dashboard, or increase the threshold for the alert, or in case the alert is not closing, you can increase the alert "Repeat Every" value of the alert to retrigger notification after a longer time period.

Check the status of similar companies and alternatives to SearchStax

Akamai
Akamai

Systems Active

Nutanix
Nutanix

Systems Active

MongoDB
MongoDB

Systems Active

LogicMonitor
LogicMonitor

Systems Active

Acquia
Acquia

Systems Active

Granicus System
Granicus System

Systems Active

CareCloud
CareCloud

Systems Active

Redis
Redis

Systems Active

integrator.io
integrator.io

Systems Active

NinjaOne Trust

Systems Active

Pantheon Operations
Pantheon Operations

Systems Active

Securiti US
Securiti US

Systems Active

Frequently Asked Questions - SearchStax

Is there a SearchStax outage?
The current status of SearchStax is: Under Maintenance
Where can I find the official status page of SearchStax?
The official status page for SearchStax is here
How can I get notified if SearchStax is down or experiencing an outage?
To get notified of any status changes to SearchStax, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of SearchStax 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 SearchStax do?
SearchStax provides comprehensive search solutions with Solr infrastructure for improved search performance on both backend and frontend.

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