Is Teamwork.com Down?

No — Teamwork.com is up

Reachable from all 8 checked regions

Average response time: 389ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.teamwork.com

Teamwork.com uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

428ms

Avg response, 30 days

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

30-day history

20-day clean streak

Jul 28 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

339ms

DNS 0ms TCP 0ms TLS 3ms TTFB 258ms

lax

277ms

DNS 0ms TCP 3ms TLS 5ms TTFB 213ms

lhr

320ms

DNS 0ms TCP 2ms TLS 5ms TTFB 245ms

nrt

609ms

DNS 0ms TCP 2ms TLS 5ms TTFB 608ms

ord

90ms

DNS 0ms TCP 2ms TLS 4ms TTFB 71ms

sin

890ms

DNS 1ms TCP 1ms TLS 3ms TTFB 672ms

sjc

304ms

DNS 0ms TCP 20ms TLS 22ms TTFB 247ms

syd

476ms

DNS 0ms TCP 100ms TLS 102ms TTFB 464ms

yyz

84ms

DNS 0ms TCP 1ms TLS 5ms TTFB 68ms

What Teamwork.com does

Teamwork.com is a project management platform aimed at client services businesses such as agencies, consultancies and studios, where billable time, budgets and profitability sit alongside tasks and milestones. The suite spans Teamwork Projects for delivery, Desk for client support tickets, Chat for internal messaging, Spaces for documentation and a CRM, all sold under one account.

What an outage looks like

Task lists and Gantt views load blank or spin, and time entries return an error instead of saving against a task. Desk tickets stop arriving from client email, so inbound requests silently queue at the mail provider. Chat messages fail to send, notification emails stop, and the mobile app shows the last cached board while writes fail. Reporting and invoicing exports may time out.

What to do about it

Check status.teamwork.com, which reports Projects, Desk, Chat, Spaces and CRM separately and splits each into US and EU regions, so an incident confined to one region or one product is visible rather than guessed at. Confirm which region your account sits in before assuming you are affected. Avoid re-logging time entries that errored until the page is green, because duplicates distort billing reports.

Is it down for everyone, or just you?

If this page says Teamwork.com 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

Teamwork.com outage FAQ

Is Teamwork down for everyone or just my account?

Not necessarily for everyone. Teamwork.com splits every major product into US and EU regional components on its status page, so an incident can affect European accounts while American ones work normally. Identify your region from the address your account loads under, then check that specific component. If the region is green, try a different project to test whether one project rather than the platform is failing.

Does a Teamwork outage affect Desk tickets from clients?

Teamwork Desk is a separate component from Projects, so support can fail while project delivery works, or the reverse. When Desk is degraded, inbound client email is not turned into tickets. Those messages generally remain at your mail provider and arrive once the component recovers, but treat anything a client says they sent during the window as unconfirmed until you actually see the ticket.

Will I lose time entries logged during an outage?

An entry that returned an error was probably never saved, while one that appeared to save normally was. Before re-entering anything, reload the task and check what is actually in the time log, because duplicate entries flow straight into billable reports and client invoices, which is considerably more work to unpick than a missing entry is to add back.

Does the Teamwork mobile app work when the website is down?

Not usually for anything that writes. The app keeps a local cache and will render the boards and tasks it last downloaded, which makes the platform look healthy from a phone while saves are quietly failing. Pull to refresh and watch for a sync error rather than trusting the data on screen, and avoid editing records that colleagues may also be changing.

How we measure this

We request Teamwork.com'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 Teamwork.com 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 Teamwork.com 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