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.

No ads · We don't sell your data

What's broken? (optional)
Is it just me?
Vendor-reported issue

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.

Official Salsify status page

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.

Checks by region

Reachable from all 4 regions we check from.

US East · ORDReachable783 ms · 31 min ago
US West · SJCReachable849 ms · 31 min ago
Europe · AMSReachable655 ms · 31 min ago
Asia-Pacific · KIXReachable1943 ms · 31 min ago

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.

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.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last checked 1 hr 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)ReportsBaselineLatencyFailed checks
Nov 600.0837 ms0
Nov 700.0763 ms0
Nov 700.0749 ms0
Nov 700.0776 ms0
Nov 700.0744 ms0
Nov 800.0662 ms0
Nov 800.0758 ms0
Nov 800.0733 ms0
Nov 800.0769 ms0
Nov 900.0680 ms0
Nov 900.0735 ms0
Nov 900.0809 ms0
Nov 900.0729 ms0
Nov 1000.0592 ms0
Nov 1000.0731 ms0
Nov 1000.0713 ms0
Nov 1000.0838 ms0
Nov 1100.0687 ms0
Nov 1100.0656 ms0
Nov 1100.0679 ms0
Nov 1100.0689 ms0
Nov 1200.0704 ms0
Nov 1200.0751 ms0
Nov 1200.0698 ms0
Nov 1200.0898 ms0
Nov 1300.0690 ms0
Nov 1300.0762 ms0
Nov 1300.0674 ms0

Reliability

Score 100/100 · grade A

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.

Salsify status badge 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

Salsify status and 30-day uptime badge

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.

Past outages

No outages on record for Salsify yet. Outages of 10 minutes or more get their own page here.

All Salsify outages · Every recent outage

Having trouble with Salsify?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

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: 730 ms average, 488–984 ms range across 13 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?

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.

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.