User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
salsify.com · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Salsify.
Estimated fix: Not enough Salsify history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 655 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 837 ms | 0 |
| Nov 7 | 0 | 0.0 | 763 ms | 0 |
| Nov 7 | 0 | 0.0 | 749 ms | 0 |
| Nov 7 | 0 | 0.0 | 776 ms | 0 |
| Nov 7 | 0 | 0.0 | 744 ms | 0 |
| Nov 8 | 0 | 0.0 | 662 ms | 0 |
| Nov 8 | 0 | 0.0 | 758 ms | 0 |
| Nov 8 | 0 | 0.0 | 733 ms | 0 |
| Nov 8 | 0 | 0.0 | 769 ms | 0 |
| Nov 9 | 0 | 0.0 | 680 ms | 0 |
| Nov 9 | 0 | 0.0 | 735 ms | 0 |
| Nov 9 | 0 | 0.0 | 809 ms | 0 |
| Nov 9 | 0 | 0.0 | 729 ms | 0 |
| Nov 10 | 0 | 0.0 | 592 ms | 0 |
| Nov 10 | 0 | 0.0 | 731 ms | 0 |
| Nov 10 | 0 | 0.0 | 713 ms | 0 |
| Nov 10 | 0 | 0.0 | 838 ms | 0 |
| Nov 11 | 0 | 0.0 | 687 ms | 0 |
| Nov 11 | 0 | 0.0 | 656 ms | 0 |
| Nov 11 | 0 | 0.0 | 679 ms | 0 |
| Nov 11 | 0 | 0.0 | 689 ms | 0 |
| Nov 12 | 0 | 0.0 | 704 ms | 0 |
| Nov 12 | 0 | 0.0 | 751 ms | 0 |
| Nov 12 | 0 | 0.0 | 698 ms | 0 |
| Nov 12 | 0 | 0.0 | 898 ms | 0 |
| Nov 13 | 0 | 0.0 | 690 ms | 0 |
| Nov 13 | 0 | 0.0 | 762 ms | 0 |
| Nov 13 | 0 | 0.0 | 674 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Salsify yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Salsify goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Salsify alerts to Slack, Discord or a webhook — free.
We track Salsify (salsify.com) as part of the Cloud & developer group. Move faster, work smarter, and scale efficiently with Salsify PXM, the intelligent product experience management platform.
Salsify publishes an official status page at status.salsify.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 730 ms average, 488–984 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public Salsify incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
730 ms on average over the last 24 hours (488–984 ms). Latest regional checks: US East 783 ms, US West 849 ms, Europe 655 ms, Asia-Pacific 1943 ms.
Yes, at https://status.salsify.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Salsify here at once, the problem is on Salsify's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Salsify. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.