awork logo

Is awork Down?

SaaSLive status, outages, and incident history

No. awork is up right now.

Every monitored awork system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment awork breaks

awork is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official awork status page
How we know: the official awork status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

awork Status Summary

As of 11:17 UTC on 14 November 2026, awork is operational. PulsAPI checked awork's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "Website unavailable", was on Nov 9, 2026 and lasted 8 min.

Cite as: PulsAPI, “awork status”, checked 14 November 2026, 11:17 UTC. https://www.pulsapi.com/services/awork

awork Component Status

The main awork systems on this page. All 8 are operational right now.

8operational
API » Core
Operational
API » Login
Operational
API » Search
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking API » Workspace, awork AI, Background Actions » Email, Background Actions » Webhooks, Web-App.

See all of them free

Component statuses may change independently during partial outages.

Recent awork Outages & Incidents

Incident history from the official awork status page, including resolution updates.

Website unavailableResolved Nov 9, 2026 · 8 minResolved

This incident has been resolved. --- [2026-11-09T17:41:34.275+01:00] (identified) Due to an issue with the website hosting provider the awork.com website is currently unavailable. The awork web app (app.awork.com) as well as our mobile and desktop apps and the API are not affected.

Information CVE-2026-98432 - security update completed / Sicherheitsupdate abgeschlossenResolved Nov 1, 2026 · 186h 26mResolved

This incident has been resolved. --- [2026-11-01T23:13:19.781+01:00] (monitoring) Security update: CVE-2026-98432 addressed We have completed the security update for the Linux kernel vulnerability CVE-2026-98432 on awork's affected production infrastructure. All affected components of our production infrastructure now run a kernel version that includes the vendor's fix. We verified the running versions after the update. These components are not directly reachable from the public internet, which limits their exposure to direct external attacks. At the time of this update, we are not aware of any exploitation of this vulnerability affecting awork. Customers do not need to take any action in connection with their use of awork. We continue to monitor developments as part of our security processes. --- Sicherheitsinformation: Sicherheitsupdate zu CVE-2026-98432 abgeschlossen Wir haben das Sicherheitsupdate für die Linux-Kernel-Schwachstelle CVE-2026-98432 auf der betroffenen Produktionsinfrastruktur von awork abgeschlossen. Alle betroffenen Komponenten unserer Produktionsinfrastruktur verwenden jetzt eine Kernel-Version mit der Fehlerkorrektur des Herstellers. Die laufenden Versionen haben wir nach dem Update geprüft. Diese Komponenten sind nicht direkt aus dem öffentlichen Internet erreichbar. Das begrenzt ihre Angriffsfläche für direkte Angriffe aus dem Internet. Zum Zeitpunkt dieser Mitteilung sind uns keine Fälle bekannt, in denen diese Schwachstelle bei awork ausgenutzt wurde. Für unsere Kundinnen und Kunden besteht im Zusammenhang mit der Nutzung von awork kein Handlungsbedarf. Wir verfolgen die weitere Entwicklung im Rahmen unserer Sicherheitsprozesse.

Partial Outage - Anthropic- ModelsResolved Oct 27, 2026 · 59 minResolved

This incident has been resolved. --- [2026-10-27T11:49:32.398+01:00] (monitoring) We're seeing recovery of Opus 5.5 --- [2026-10-27T11:01:35.579+01:00] (identified) Sonnet 5.5 and Haiku 5.5 remain available and only Opus 5.5 is impacted. --- [2026-10-27T11:01:51.436+01:00] (identified) We are seeing a partial outage with Anthropic- models, particularly Opus 5.5.

awork Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a awork incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live awork Outage Reports

Problems reported by engineers using awork. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No awork problems reported yet.

Something wrong with awork on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About awork

awork posts its status at status.awork.com. The page covers 8 components, among them Core (Projects, Tasks, Time Tracking), Login and Search. Past incidents and uptime for awork stay on this page, which helps when you want to know how often it has trouble.

awork Status FAQ

Is awork down right now?

The verdict at the top of this page comes from the latest poll of the official awork status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if awork is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until awork recovers.

How do I check awork uptime history?

PulsAPI tracks awork uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever awork changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect awork outages?

PulsAPI reads the official awork status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual awork components?

Yes. PulsAPI monitors 8 individual awork components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when awork goes down?

Yes. Create a free account and subscribe to awork: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with awork to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot awork problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor awork?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so awork plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track awork with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services