Skip to main content

Is Basecamp Down?

No — Basecamp is up

Reachable from all 8 checked regions

Average response time: 175ms

Last checked · checks run every 6 hours

Official status page: https://www.37status.com

Basecamp uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
171ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 40 checks
Aug 4: 100.00% uptime, 52 checks
Aug 5: 100.00% uptime, 40 checks
Aug 6: 100.00% uptime, 40 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 38 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
178ms
DNS 0ms TCP 2ms TLS 19ms TTFB 174ms
arn
167ms
DNS 0ms TCP 1ms TLS 10ms TTFB 162ms
bom
262ms
DNS 0ms TCP 2ms TLS 9ms TTFB 259ms
cdg
152ms
DNS 0ms TCP 2ms TLS 8ms TTFB 149ms
dfw
154ms
DNS 0ms TCP 1ms TLS 14ms TTFB 143ms
ewr
117ms
DNS 1ms TCP 8ms TLS 11ms TTFB 113ms
sjc
95ms
DNS 0ms TCP 3ms TLS 14ms TTFB 90ms
syd
268ms
DNS 0ms TCP 1ms TLS 8ms TTFB 264ms
yyz
104ms
DNS 0ms TCP 1ms TLS 8ms TTFB 101ms

What Basecamp does

Basecamp is the project management tool from 37signals, built around message boards, to-do lists, schedules and chat inside a single space per project. It is used mostly by small teams and agencies as the central place work gets discussed, so an outage stops coordination rather than breaking anything customer-facing.

What an outage looks like

37signals runs several generations of Basecamp at once and tracks them separately, so an incident can hit one and leave the others alone. Teams on an older version can be unaffected while current customers are down, or the reverse. Because Basecamp holds discussion rather than production traffic, the first sign is usually a page that will not load rather than an alert.

What to do about it

Check 37status.com, the shared status page for all 37signals products. It lists Basecamp 5, Basecamp 2 and Basecamp Classic as separate components alongside HEY, each with 90 days of uptime history, so confirm which version your account is on before reading a line. A historical uptime view sits behind the current one if you need to see a pattern.

Is it down for everyone, or just you?

If this page says Basecamp is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Basecamp outage FAQ

Which Basecamp version am I on, and does it matter?
It matters, because 37signals tracks each generation separately. The status page lists Basecamp 5, Basecamp 2 and Basecamp Classic as distinct components with their own uptime figures, and older accounts often stay on older versions for years. Check the address your team actually uses before concluding from a green page that your version is fine.
Does a Basecamp outage affect HEY email?
Not necessarily, because they are separate products on the same status page. 37signals lists HEY alongside the Basecamp versions with its own uptime figure, and the company runs both, which is why one page covers them all. A shared infrastructure problem can hit both at once, but each carries its own line to read.
Why does status.basecamp.com not look like a Basecamp page?
It resolves to 37status.com, the status page 37signals publishes for its whole product line. The company name rather than the product name is the one on the page, which is why searching for a Basecamp-specific status site is confusing. Both addresses reach the same dashboard, and Basecamp is listed by name once you are there.
How much uptime history does 37signals publish?
Ninety days per component, with a historical uptime view behind it. Each Basecamp generation and HEY carries its own percentage across that window, so you can see whether a version has been consistently reliable rather than only whether it is up at this moment. That is more than most project management vendors show.

How we measure this

  • We request Basecamp's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the 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 Basecamp publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Basecamp goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required