User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
salsify.com · Cloud & developer
Is Salsify down?
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.
What to try while Salsify is having problems
Estimated fix: Not enough Salsify history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → salsify.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 42 min ago. Last stored result reached it in 655 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 820 ms | 0 |
| Mon 17 | 0 | 0.0 | 756 ms | 0 |
| Mon 19 | 0 | 0.0 | 875 ms | 0 |
| Mon 21 | 0 | 0.0 | 729 ms | 0 |
| Mon 23 | 0 | 0.0 | 719 ms | 0 |
| Tue 01 | 0 | 0.0 | 647 ms | 0 |
| Tue 04 | 0 | 0.0 | 592 ms | 0 |
| Tue 06 | 0 | 0.0 | 731 ms | 0 |
| Tue 08 | 0 | 0.0 | 826 ms | 0 |
| Tue 10 | 0 | 0.0 | 727 ms | 0 |
| Tue 12 | 0 | 0.0 | 713 ms | 0 |
| Tue 14 | 0 | 0.0 | 814 ms | 0 |
| Tue 17 | 0 | 0.0 | 687 ms | 0 |
| Tue 19 | 0 | 0.0 | 686 ms | 0 |
| Tue 21 | 0 | 0.0 | 959 ms | 0 |
| Tue 23 | 0 | 0.0 | 838 ms | 0 |
| Wed 02 | 0 | 0.0 | 692 ms | 0 |
| Wed 04 | 0 | 0.0 | 639 ms | 0 |
| Wed 06 | 0 | 0.0 | 656 ms | 0 |
| Wed 08 | 0 | 0.0 | 710 ms | 0 |
| Wed 11 | 0 | 0.0 | 585 ms | 0 |
| Wed 13 | 0 | 0.0 | 756 ms | 0 |
| Wed 15 | 0 | 0.0 | 679 ms | 0 |
| Wed 17 | 0 | 0.0 | 652 ms | 0 |
| Wed 19 | 0 | 0.0 | 697 ms | 0 |
| Wed 21 | 0 | 0.0 | 673 ms | 0 |
| Wed 23 | 0 | 0.0 | 689 ms | 0 |
| Thu 02 | 0 | 0.0 | 764 ms | 0 |
| Thu 04 | 0 | 0.0 | 644 ms | 0 |
| Thu 06 | 0 | 0.0 | 698 ms | 0 |
| Thu 08 | 0 | 0.0 | 768 ms | 0 |
| Thu 10 | 0 | 0.0 | 751 ms | 0 |
| Thu 12 | 0 | 0.0 | 668 ms | 0 |
| Thu 14 | 0 | 0.0 | 775 ms | 0 |
| Thu 16 | 0 | 0.0 | 698 ms | 0 |
| Thu 18 | 0 | 0.0 | 898 ms | 0 |
| Thu 20 | 0 | 0.0 | 902 ms | 0 |
| Thu 22 | 0 | 0.0 | 661 ms | 0 |
| Fri 00 | 0 | 0.0 | 488 ms | 0 |
| Fri 02 | 0 | 0.0 | 690 ms | 0 |
| Fri 05 | 0 | 0.0 | 692 ms | 0 |
| Fri 07 | 0 | 0.0 | 762 ms | 0 |
| Fri 09 | 0 | 0.0 | 714 ms | 0 |
| Fri 11 | 0 | 0.0 | 821 ms | 0 |
| Fri 12 | 0 | 0.0 | 674 ms | 0 |
| Fri 13 | 0 | 0.0 | 799 ms | 0 |
| Fri 15 | 0 | 0.0 | 815 ms | 0 |
| Fri 17 | 0 | 0.0 | 655 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Salsify badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Salsify yet. Outages of 10 minutes or more get their own page here.
Having trouble with Salsify?
One report per service every 10 minutes from this network. No account.
Follow Salsify
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.
About Salsify
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: 742 ms average, 488–984 ms range across 14 successful checks.
Questions
Is Salsify down right now?
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)
When was Salsify last down?
We have not recorded a public Salsify incident since monitoring began 8 days ago.
What is Salsify's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Salsify respond?
742 ms on average over the last 24 hours (488–984 ms).
Does Salsify have an official status page?
Yes, at https://status.salsify.com.
Salsify not working for me but the status is fine. What now?
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.