Skip to main content
Wrike logo

Is Wrike Down?

No — Wrike is up

Reachable from all 8 checked regions

Average response time: 286ms

Last checked · checks run every 6 hours

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

Wrike uptime

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

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

30-day history

25-day clean streak
Sep 13: blocked from automated checks
Sep 14: blocked from automated checks
Sep 15: blocked from automated checks
Sep 16: blocked from automated checks
Sep 17: 100.00% uptime, 30 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 31 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 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.

fra
268ms
DNS 131ms TCP 1ms TLS 9ms TTFB 267ms
gru
494ms
DNS 126ms TCP 2ms TLS 12ms TTFB 494ms
iad
171ms
DNS 119ms TCP 1ms TLS 11ms TTFB 171ms
jnb
514ms
DNS 218ms TCP 0ms TLS 12ms TTFB 514ms
lax
196ms
DNS 80ms TCP 2ms TLS 10ms TTFB 195ms
lhr
168ms
DNS 34ms TCP 2ms TLS 10ms TTFB 168ms
nrt
297ms
DNS 87ms TCP 1ms TLS 10ms TTFB 296ms
ord
186ms
DNS 57ms TCP 2ms TLS 11ms TTFB 185ms

What Wrike does

Wrike is a work management platform for teams, covering tasks, folders and projects, timelines, request forms, time tracking, proofing and reporting through Wrike Analyze. Agencies, marketing teams, professional services firms and product groups run client and internal delivery on it, so an outage stops the place where a team's assignments, due dates and approvals actually live.

What an outage looks like

Wrike runs separate US and EU data centres and posts incidents against one or both, so colleagues on the other region can be entirely unaffected. Its published incidents describe the workspace failing to load, 502 errors on the login page, and Timesheets entries or submissions failing while the rest of the product works. Task descriptions have gone unavailable during scheduled maintenance windows.

What to do about it

Check status.wrike.com, which shows current status, scheduled maintenance and a dated history of incidents and completed maintenance. Note which data centre an incident names, since only accounts hosted in that region are affected and a colleague elsewhere is not a useful test. Wrike publishes maintenance windows there in advance, including short periods where email integrations or task descriptions may be unavailable.

Is it down for everyone, or just you?

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

Test it yourself

Related services

Wrike outage FAQ

Is Wrike down for everyone or just my team?
Wrike operates separate US and EU data centres and reports incidents against a specific one, so an outage can be real for your account and invisible to a colleague on the other region. Asking someone else whether Wrike works is only meaningful if they are on the same data centre. The status page names the affected region, which is the fastest way to settle it.
Why can I not log in when Wrike says it is operational?
Wrike has previously recorded incidents where the workspace returned a 502 specifically on the login page while other functionality was fine, and those are posted as their own entries. A scheduled maintenance window can also produce short sign-in interruptions. Check the recent updates list on the status page rather than only the top banner, since resolved and in-progress entries carry the detail.
Will I lose work if Wrike goes down mid-edit?
Wrike saves changes to the server as you work, so committed edits generally survive. The exposure is anything in an unsent state at the moment of failure, and features that Wrike has flagged individually during incidents, such as Timesheets submissions failing while the rest of the product worked. If a timesheet or form submission errored, confirm it landed rather than assuming.
Does Wrike schedule maintenance in advance?
Yes, and it posts the windows on the status page with dates, times in UTC and the data centres involved. Recent entries describe short interruptions during those windows, including email integrations being unavailable for a few minutes and task descriptions briefly not loading. If you hit a problem at a round hour on a weekend, checking the scheduled maintenance section first is usually quicker than debugging.

How we measure this

  • We request Wrike's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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 Wrike 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 Wrike goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required