Is Clockwise Down Right Now? Check if there is a current outage ongoing.

We are currently investigating this issue

We are currently investigating this issue.

This incident was resolved July 15. We are updating the status page late.

A fix has been implemented and we are monitoring the results. Users will need to update to the latest version of the extension for the fix to be enabled.

We are continuing to work on a fix for this issue.

Currently identifying a fix for an issue that may make the flexible meeting toggle not appear for some users in Google Calendar. In the meantime, you should be able to toggle flexible meetings in our own calendar: https://www.getclockwise.com/app/ai

This morning, we received reports that Links were not displaying available times for some users. Upon investigation, we found and mitigated the issue by rolling back some code.

This incident has been resolved.

Google has said they have fixed the underlying issue that caused the issue. It should no longer impact Clockwise users.

It appears that users should be able to log back into Clockwise, however Google's status page says they are still identifying a full solution to the problem, so some issues may persist.

A fix has been implemented and we are monitoring the results.

Google Workspace is currently experiencing an outage, according to their status page, which is impacting our services, and leading to some users no longer having access. We are currently waiting for Google to resolve this issue. We will update you when we have more information.

We are currently investigating an issue that is preventing some users from accessing Clockwise. We will provide an update when we have more information.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We've currently investigating a potential issue with our Scheduling Links feature where Focus Time blocks are identified as busy and made unavailable for booking.

We are currently investigating this issue.

We have cleaned up all known duplicate events. If you have any further questions, please reach out to our support team. Thank you!

We're continuing to work on removing duplicated events from roughly 1,000 users' calendars. We're being thorough to ensure we only delete duplicated events. We'll keep providing updates as we continue to work on resolution.

Cleanup is on-going; we're being cautious to not introduce more problems. We have code changes in place to identify duplicated events. This will run overnight. Our expectation is that we'll remove duplicated events sometime tomorrow. Apologies to any impacted users for the inconvenience.

We're continuing to work on cleaning up any impacted calendars and events.

We've identified an issue with Clockwise that results in some recurring meetings managed by Clockwise being duplicated. We've rolled back the problematic changes so no new meetings should be duplicated. We're now moving onto cleaning up any impacted calendars. We'll keep providing updates as we continue to work on resolution.

This incident has been resolved.

We've identified the issue with our Slack status sync infrastructure that caused the outage and deployed a fix. Slack sync should be reporting the correct status for all users within the hour.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Our current Slack sync is experiencing an outage and might be reporting an After Hours status even for users within their working hours. Our team is currently investigating the root cause.

Our current Slack sync is experiencing an outage and might be reporting an After Hours status even for users within their working hours. Our team is currently investigating the root cause.

We are currently investigating this issue.

This incident has been resolved.

We believe we've isolated the incident and have deployed a change that fixed the issue. All product features should be working normally. We will continue to monitor the situation and provide updates as needed.

A fix has been implemented and we are monitoring the results.

While our site should now be responsive for most users, many features have been turned off, such as goal shuffling and Slack statuses, while we continue to investigate the underlying cause.

An incident has occurred that has led to the site being degraded for some users. We are still investigating the cause.

We are currently investigating this issue.

Earlier today we had an incident that briefly affected real time calendar event updates. Potentially, some changes made during this time around setting up smartholds or color coding may not immediately display, but they will show up within the next few hours.

This incident has been marked as resolved

Final update as we are marking the issue as resolved. After digging through some more, the issue happens consistently when using a particular OAuth provider, but we were not able to reproduce the issue with using our regular OAuth signup flow.

A hotfix for a particular edge case in relation to this issue is being deployed.

Customer impact is significantly lower than we originally estimated and only affect particular users. Most signups are still successful. We're still working on determining the cause of the failure.

We're currently investigating an issue that is preventing some customers from signing in or up using Slack's OAuth flow. We're currently investigating.

We are currently investigating this issue.

This incident has been resolved.

This incident has been resolved.

We've identified the issue and rolled out a fix. We're monitoring now to confirm full restoration of performance.

We are currently investigating an issue resulting in slow or degraded performance of Clockwise. We'll provide updates here as we identify and mitigate this issue. Thank you for your patience.

Google Calendar's partial outage appears to be resolved. We'll continue to actively monitor.

Google Calendar's partial outage is still on-going. We're actively monitoring and will continue to provide updates as we learn more.

Google Calendar is undergoing what looks like a partial outage impacting all its users. As a result, Clockwise has delayed information about changes to calendars. This will appear like newly created or updated calendar events not appearing in Clockwise and delays to rescheduling Flexible Meetings, Focus Time blocks, Personal Calendar sync, etc. We'll continue to monitor the situation here and will get everything working again as soon as Google Calendar makes improvements to their systems.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're in progress on deploying a fix to production. We'll continue to provide updates as we have them.

The issue has been identified and a fix is in progress.

We are continuing to investigate this issue. We've taken steps to minimize further impact and we're working to remove duplicated Focus Time holds from any impacted calendars.

We are continuing to investigate this issue.

We are currently investigating an issue related to duplicate Focus Time slots being created.

The issue has been resolved.

A fix has been implemented and operations seem to be returning to normal

We have detected an increase of errors in Clockwise services. We are investigating the issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue resulting in slow or degraded performance of Clockwise.

The fix we put in place around 11:30AM PDT has resolved this issue.

A fix has been implemented and we are monitoring the results.

We've identified the cause of this incident. Our engineers are working on a fix.

Our automated systems have detected that users attempting to access Clockwise may see slow load times or errors. Our engineers are investigating. We'll provide updates here.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Our monitoring indicates access times and error rates have returned to normal levels. We'll continue investigating and monitoring to prevent this from reoccurring.

Our automated systems have detected that users attempting to access Clockwise may see slow load times or errors. Our engineers are investigating. We'll provide updates here.

This incident has been resolved.

We've corrected the misconfiguration and error rates appear to be back at normal levels. We'll continue to monitor the situation for a few more minutes before fully resolving this incident.

We've identified a potential misconfiguration with our load balancer fleet and are moving to mitigate it.

We're seeing elevated error rates when using Clockwise. Our on-call engineers are investigating. We'll provide updates here as our investigation progresses.

This incident has been resolved.

We've implemented several fixes that appear to have resolved the issue. We'll continue monitoring the situation to ensure Clockwise is working correctly.

We are continuing to work on a fix for this issue.

We've identified an issue causing elevated error rates when attempting to use Clockwise. We're hard at work on a fix and will post an update here when we've resolved the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are receiving reports of issues with sign up and log in. We are currently identifying the issue and will update soon.

This incident has been resolved.

The issue has been mitigated and we are monitoring for any further performance degradation.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been put in place and we are monitoring.

We have identified the problem and are preparing a fix.

We are currently investigating the issue.

Incident has been resolved.

We have detected elevated API errors, resulting in degraded performance of all Clockwise clients. We have identified the issue and have rolled out a fix. In the meantime, performance may be slower than expected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.