Skip to main content
Searchspring logo

Is Searchspring Down?

No — Searchspring is up
Searchspring's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 246 ms

Right now

The verdict is the worse of these two. How we decide

Searchspring's status page

status.searchspring.com · read · checked every 3 minutes

Operational
Searchspring's components, as its status page reports them
ComponentStatus
SearchOperational
IndexingOperational
AutocompleteOperational
SMC ( Searchspring Management Console )Operational
Product Recommendation WidgetsOperational

FlareWarden checks

searchspring.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
246 ms
Checked

By region

  • Ashburn reachable, 145 ms
  • Dallas reachable, 154 ms
  • Frankfurt reachable, 137 ms
  • Johannesburg reachable, 635 ms
  • London reachable, 84 ms
  • Los Angeles reachable, 206 ms
  • Newark reachable, 139 ms
  • São Paulo reachable, 470 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn36 ms1 ms18 ms143 ms
Dallas67 ms1 ms10 ms151 ms
Frankfurt102 ms2 ms14 ms134 ms
Johannesburg279 ms1 ms12 ms631 ms
London43 ms3 ms13 ms81 ms
Los Angeles153 ms2 ms21 ms202 ms
Newark29 ms2 ms14 ms136 ms
São Paulo243 ms4 ms18 ms467 ms
We check that searchspring.com loads, not every feature behind it. Test it yourself

History

Incidents Searchspring reported

Since Oct 22, 15 days · from status.searchspring.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Searchspring website availability

Measured by FlareWarden · searchspring.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
197ms

Last 30 days

37-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 31 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of searchspring.com from multiple regions every 6 hours. Searchspring's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 37 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Searchspring does

Searchspring provides site search, autocomplete, category page merchandising and product recommendations for online stores, including stores on Shopify, BigCommerce and Magento. It is now a division of Athos Commerce, which combined Searchspring with Klevu and Intelligent Reach, and its management console has been rebranded as the Athos Console. Searchspring indexes each store's product feed and serves results to shoppers through its search API, so its outages show on the storefront.

What an outage looks like

Shoppers see search and category pages that return no products or an error, and autocomplete stops suggesting items; past incidents logged 500, 503 and 504 errors from the search API. Merchants see different faults: product changes that do not appear because indexing is queued or failing, a management console that will not load or apply merchandising changes, and Also Viewed or Also Bought widgets that disappear.

What to do about it

Check status.searchspring.com, linked from both searchspring.com and athoscommerce.com, for the Search, Indexing, Autocomplete, SMC and Product Recommendation Widgets rows. For a storefront-breaking fault, submit a request at help.searchspring.net with Urgent in the subject line, which pages the 24/7 on-call engineer. Tickets emailed to support@searchspring.com are closed automatically. After indexing recovers, press Update Index to resync products sooner.

Is it down for everyone, or just you?

If this page says Searchspring is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Searchspring outage FAQ

Is Searchspring down for everyone or just my store?
Often only for a subset of stores. Past incidents include 503 errors on a small subset of sites, search errors limited to the Australia region, and a BigCommerce template change that left some Snap-powered listing pages empty while Searchspring's core search kept working. If the status page is green, check recent changes to your theme or platform before opening a ticket.
Is Searchspring now Athos Commerce?
Yes. Searchspring's website says Searchspring is now Athos Commerce, a company that unites Searchspring, Klevu and Intelligent Reach, and calls itself a division of it. The management console has been rebranded as the Athos Console. Both websites link status.searchspring.com, and Athos also runs status.athoscommerce.com with its own Athos Console, Data Sync, Search, Autocomplete and Recommendations Widgets rows, so check both if one looks clear.
Does an AWS outage affect Searchspring?
It can. During the AWS us-east outage on October 20, 2025, Searchspring's search API went down, the management console was put into maintenance mode so no changes could be made, and indexing and reporting took until that evening to recover. Searchspring said traffic in us-west and other regions was unaffected. Search and autocomplete were fully back about two hours before indexing.
Why aren't my product changes showing in Searchspring?
Usually indexing is behind rather than search being down. Searchspring syncs your catalog on a schedule, staggered by up to 50 percent of your interval, and Live Indexing covers only Shopify and JSON feed sites. The Index Status page shows the last completed and next scheduled index, and Update Index adds your site to the queue. When the Indexing row reports a high queue, expect delays.
What counts as urgent for Searchspring support?
Searchspring treats a fault as urgent when it stops Searchspring working on your site: all products missing from a Searchspring-powered listing page, several category pages with no results, wrong images, names or pricing on all products, results that do not link to product pages, indexing failures, or an unusable management console. Put Urgent in the subject of a help.searchspring.net request to page the on-call engineer, who aims to respond within 60 minutes.

How we measure this

  • We request Searchspring's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Searchspring publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Searchspring itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Searchspring goes down

We check Searchspring every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required