Is Wrike Down?

No — Wrike is up

Wrike's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 229 ms

Right now

We could not read Wrike's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

Reachable

Regions up: 8 of 8
Response: 229 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 279 ms
Dallas reachable, 136 ms
Frankfurt reachable, 208 ms
Newark reachable, 84 ms
Paris reachable, 167 ms
Stockholm reachable, 207 ms
Sydney reachable, 550 ms
Toronto reachable, 207 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	68 ms	4 ms	15 ms	278 ms
Dallas	45 ms	2 ms	9 ms	136 ms
Frankfurt	51 ms	1 ms	8 ms	208 ms
Newark	32 ms	1 ms	8 ms	84 ms
Paris	35 ms	2 ms	9 ms	167 ms
Stockholm	49 ms	1 ms	8 ms	207 ms
Sydney	228 ms	1 ms	6 ms	531 ms
Toronto	80 ms	2 ms	9 ms	207 ms

We check that login.wrike.com loads, not every feature behind it. Test it yourself

History

Wrike website availability

Measured by FlareWarden · login.wrike.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 256ms

Last 30 days

36-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of login.wrike.com from multiple regions every 6 hours. Wrike's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Wrike itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Wrike goes down

We check Wrike every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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