Is When I Work Down?

No — When I Work is up

When I Work's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 621 ms

Right now

The verdict is the worse of these two. How we decide

When I Work's status page

status.wheniwork.com · read 1 minute ago · checked every 3 minutes

Operational

When I Work's components, as its status page reports them
Component	Status
Web App	Operational
API	Operational
Login	Operational
Website	Operational
Workchat	Operational

Open their status page

FlareWarden checks

wheniwork.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 621 ms
Checked: 18 minutes ago

By region

Amsterdam reachable, 489 ms
Chicago reachable, 202 ms
London reachable, 409 ms
San Jose reachable, 344 ms
Singapore reachable, 1298 ms
Sydney reachable, 1152 ms
Tokyo reachable, 878 ms
Toronto reachable, 199 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	91 ms	4 ms	8 ms	471 ms
Chicago	37 ms	1 ms	3 ms	194 ms
London	87 ms	1 ms	3 ms	401 ms
San Jose	88 ms	1 ms	4 ms	337 ms
Singapore	229 ms	139 ms	140 ms	732 ms
Sydney	158 ms	136 ms	138 ms	607 ms
Tokyo	123 ms	103 ms	106 ms	449 ms
Toronto	29 ms	8 ms	12 ms	167 ms

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

History

Incidents When I Work reported

Since Oct 22, 4 days · from status.wheniwork.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

When I Work website availability

Measured by FlareWarden · wheniwork.com

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

Last 30 days

25-day clean streak

Sep 26 Today

No downtime Partial Downtime Not measurable No data

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

What When I Work does

When I Work is a scheduling and time tracking app for businesses with hourly staff. Managers build and publish shifts, approve time off and review timesheets in the web app, while employees check schedules, pick up open shifts, clock in and out and message coworkers in WorkChat from the iOS and Android apps or a shared Time Clock Terminal. Timesheets can be sent on to payroll integrations such as Gusto.

What an outage looks like

Login fails or pages keep loading in the web and mobile apps. The vendor's past incident updates describe error messages or long delays when creating or picking up shifts, loading timesheets, clocking in or out and adding users. A Time Clock Terminal may keep loading without responding when staff punch. WorkChat can become unavailable on every platform, and SMS notifications, Teamtxt messages and verification codes can stop arriving.

What to do about it

Check status.wheniwork.com, which lists the Web App, API, Login, Website and Workchat separately and offers email, SMS and RSS updates. During past incidents the vendor advised retrying the action a few minutes later. If staff cannot clock in, record their start and end times another way; a manager can add the missing entries by editing timesheets once the app recovers. Support is by ticket or live chat, not phone.

Is it down for everyone, or just you?

If this page says When I Work 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

When I Work outage FAQ

Is When I Work down for everyone or just me?

Compare the multi-region checks on this page with status.wheniwork.com, which reports the Web App, API, Login, Website and Workchat as separate components. If both look healthy, the problem is likely local: the vendor's troubleshooting guides suggest updating the mobile app, clearing its cache or reinstalling it, and checking that the computer running a Time Clock Terminal still has a working internet connection.

What happens to clock-ins missed during a When I Work outage?

A manager or admin can add them afterwards by manually editing the employee's timesheet, which is the fix When I Work's own help articles give when a punch could not be made in the app. Have staff note their actual start, break and end times on paper or in a message while the outage lasts, so the entries can be added accurately once the service is back.

How do I contact When I Work support during an outage?

Submit a ticket through the Need Help button in the web app or the mobile app, or email support@wheniwork.com. When I Work does not offer phone support. Live chat is open to admins, managers and supervisors from 7 a.m. to 7 p.m. Central on weekdays, tickets are answered 7 a.m. to 9 p.m. Central on weekdays, and both run 9 a.m. to 4:30 p.m. Central on weekends.

Does a WorkChat outage affect scheduling and the time clock?

Not necessarily. WorkChat is listed as its own component on the When I Work status page, and several past incidents were listed against WorkChat alone. Incidents on the Web App, API or Login components are the ones whose updates described failed shift changes, timesheets and clock-ins. An SMS outage covering notifications, Teamtxt and verification codes was also reported as its own incident.

How long do When I Work outages usually last?

Most incidents on the When I Work status page were resolved within a few hours, and the shortest login problem was fixed in under 15 minutes. Performance problems have run longer: one round of slow loading and errors across web, iOS and Android stayed open for more than two weeks while fixes were released, with service improving for most customers along the way.

How we measure this

We request When I Work'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 When I Work 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 When I Work 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. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when When I Work goes down

We check When I Work 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