awork.com

All Systems Operational

Uptime over the past 90 days. View historical uptime.
Web-App Operational
90 days ago
99.9 % uptime
Today
API Operational
90 days ago
99.98 % uptime
Today
Login Operational
90 days ago
99.99 % uptime
Today
Core (Projects, Tasks, Time Tracking) Operational
90 days ago
99.96 % uptime
Today
Workspace Operational
90 days ago
99.98 % uptime
Today
Search Operational
90 days ago
99.99 % uptime
Today
Background Actions Operational
90 days ago
99.99 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Email Operational
90 days ago
99.98 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
Web-App response time
Fetching
Login response time
Fetching
Projects, Tasks, Time Tracking response time
Fetching
Workspace response time
Fetching
Search response time
Fetching
Email response time
Fetching
Mar 11, 2026
Tasks from task filters not loading
Resolved - This incident has been resolved.
Mar 11, 10:17 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 11, 09:56 CET
Identified - We have found the reason and are deploying a fix.
Mar 11, 09:46 CET
Investigating - We are currently investigating reports that tasks do not load when opened from task filters. We are able to reproduce this and are working on a fix.
Mar 11, 09:26 CET
Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

No incidents reported.

Mar 4, 2026

No incidents reported.

Mar 3, 2026

No incidents reported.

Mar 2, 2026
awork slow or unavailable
Postmortem - Read details
Mar 2, 14:24 CET
Resolved - This incident has been resolved.
Mar 2, 11:31 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 10:37 CET
Update - We are continuing to work on a fix for this issue.
Mar 2, 10:18 CET
Update - We have found the cause but the implemented measures have not resulted in the expected resolution yet.
Mar 2, 10:12 CET
Update - We are continuing to work on a fix for this issue.
Mar 2, 10:11 CET
Update - We are still investigating and while we have found the root cause of the issue, the implemented measures have not resulted in the solution as expected. We are continuing to look for a permanent solution.
Mar 2, 10:09 CET
Identified - We are implementing a fix to improve the performance for all users.
Mar 2, 09:43 CET
Investigating - Some users may be experience reduced performance
Mar 2, 09:27 CET
Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026
awork slow or unavailable
Resolved - Database is stable again. We saw a huge amount of clients reconnecting around 9:30h triggering the incident and we are implementing further improvements to handle this better in the future.
Feb 27, 11:31 CET
Monitoring - We implemented a fix and monitoring the results.
Feb 27, 10:31 CET
Investigating - We are seeing an increased load on the database and are investigating.
Feb 27, 09:46 CET
Feb 26, 2026
awork slow or unavailable
Postmortem - Read details
Feb 26, 14:20 CET
Resolved - Database is stable again. We will provide a Post-Mortem for this incident later today.
Feb 26, 11:24 CET
Update - Database has recovered but we are still monitoring and investigating the root cause.
Feb 26, 10:39 CET
Monitoring - We implemented a fix and are monitoring the results.
Feb 26, 10:33 CET
Identified - We are seeing an increased database load and working on a solution.
Feb 26, 09:43 CET
Feb 25, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage