37signals logo

Is 37signals Down?

SaaSLive status, outages, and incident history

No. 37signals is up right now.

Every monitored 37signals system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 5m agoLive · every 60s

Know the moment 37signals breaks

37signals is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official 37signals status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

37signals Status Summary

As of 19:10 UTC on 14 November 2026, 37signals is operational. PulsAPI checked 37signals's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "Campfire outage", was on Nov 10, 2026 and lasted 6 min.

Cite as: PulsAPI, “37signals status”, checked 14 November 2026, 19:10 UTC. https://www.pulsapi.com/services/37signals

37signals Component Status

The main 37signals systems on this page. All 8 are operational right now.

8operational
Backpack
Operational
Basecamp 2
Operational
Basecamp 5
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Basecamp Classic, Campfire, Fizzy, HEY, Highrise.

See all of them free

Component statuses may change independently during partial outages.

Recent 37signals Outages & Incidents

Incident history from the official 37signals status page, including resolution updates.

Campfire outageResolved Nov 10, 2026 · 6 minResolved

Campfire is back up and operating normally. --- [2026-11-10T03:04:31.557Z] (investigating) Campfire is down. We are investigating.

Basecamp Classic outageResolved Oct 21, 2026 · 5 minResolved

Basecamp Classic is back up and operating normally. --- [2026-10-21T01:20:30.487Z] (investigating) Basecamp Classic is down. We are investigating.

Campfire outageResolved Oct 20, 2026 · 6 minResolved

Campfire is back up and operating normally. --- [2026-10-20T21:27:31.219Z] (investigating) Campfire is down. We are investigating.

37signals Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a 37signals incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live 37signals Outage Reports

Problems reported by engineers using 37signals. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No 37signals problems reported yet.

Something wrong with 37signals on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About 37signals

Is 37signals down? Its official status page at www.37status.com reports on 8 components, including Backpack, Basecamp 2 and Basecamp 5. PulsAPI checks it every few minutes and can alert you when 37signals reports an incident.

37signals Status FAQ

Is 37signals down right now?

The verdict at the top of this page comes from the latest poll of the official 37signals status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if 37signals is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until 37signals recovers.

How do I check 37signals uptime history?

PulsAPI tracks 37signals uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever 37signals changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect 37signals outages?

PulsAPI reads the official 37signals status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual 37signals components?

Yes. PulsAPI monitors 8 individual 37signals components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when 37signals goes down?

Yes. Create a free account and subscribe to 37signals: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with 37signals to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot 37signals problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor 37signals?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so 37signals plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track 37signals with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services