- Service Status
- /
- Searchspring

Is Searchspring Down?
- 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
| Component | Status |
|---|---|
| Search | Operational |
| Indexing | Operational |
| Autocomplete | Operational |
| SMC ( Searchspring Management Console ) | Operational |
| Product Recommendation Widgets | Operational |
FlareWarden checks
searchspring.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 36 ms | 1 ms | 18 ms | 143 ms |
| Dallas | 67 ms | 1 ms | 10 ms | 151 ms |
| Frankfurt | 102 ms | 2 ms | 14 ms | 134 ms |
| Johannesburg | 279 ms | 1 ms | 12 ms | 631 ms |
| London | 43 ms | 3 ms | 13 ms | 81 ms |
| Los Angeles | 153 ms | 2 ms | 21 ms | 202 ms |
| Newark | 29 ms | 2 ms | 14 ms | 136 ms |
| São Paulo | 243 ms | 4 ms | 18 ms | 467 ms |
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 streakMeasured 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.
Related services
Searchspring outage FAQ
Is Searchspring down for everyone or just my store?
Is Searchspring now Athos Commerce?
Does an AWS outage affect Searchspring?
Why aren't my product changes showing in Searchspring?
What counts as urgent for Searchspring support?
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
403or429means 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


