DocuSign Outage History
Uptime record, past incidents, and downtime history for DocuSign.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| July 2026 | 44.4% | 9 | 5 |
| June 2026 | 20% | 30 | 24 |
| May 2026 | 61.3% | 31 | 12 |
| April 2026 | 81% | 21 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
Errors accessing the sending web application (Incident 5334)
Started: Jul 7, 8:55 PM
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance.
An update will be provided when a significant update is available.
Jul 8, 3:50 PM
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance.
An update will be provided when a significant update is available.
Jul 8, 3:39 AM
investigating
We are continuing to investigate the web cache issue. A small subset of customers may see an error when accessing the send web application page. Completely emptying the browser cache and trying again is a viable fix.
Updates will be posted when there is a significant update.
Jul 8, 12:10 AM
investigating
We continue to investigate and have engaged external vendor resources
Jul 7, 11:54 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jul 7, 10:26 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jul 7, 10:01 PM
investigating
We are continuing to investigate this issue.
Jul 7, 9:37 PM
investigating
A small subset of customers may see errors accessing the sending web application. We are actively investigating the underlying cause.
Jul 7, 8:55 PM
Intermittent Issues With Delivery of e-mail Notifications (Incident 5326)
Started: Jul 7, 3:31 PM
identified
A subset of customers may experience intermittent failures of email notifications upon sending of envelopes. To mitigate this customers can log into their DocuSign account and access the envelope directly. Engineering teams have identified the issue and are currently working to resolve this issue.
Jul 7, 3:31 PM
Intermittent Errors and Delays (Incident 5312)
Started: Jul 5, 10:35 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 5, 10:50 PM
investigating
We are actively investigating this issue.
Jul 5, 10:35 PM
June 2026
Customers may experience latency (Incident 5259)
Started: Jun 30, 11:18 AM
identified
We have identified the issue and a fix is being implemented.
Jul 1, 2:57 PM
investigating
We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.
Jul 1, 12:57 AM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 30, 10:55 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 30, 8:34 PM
investigating
We are continuing to investigate this issue.
Jun 30, 12:36 PM
investigating
We are actively investigating this issue.
Jun 30, 11:18 AM
Some customers may experience errors with Sending and Signing (Incident 5252)
Started: Jun 30, 12:25 AM
identified
We have identified the issue and a fix is being implemented.
Jun 30, 12:26 AM
investigating
We are actively investigating this issue.
Jun 30, 12:25 AM
Customers may experience errors with Sending and Signing in NA3 (Incident 5247)
Started: Jun 29, 9:32 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 29, 9:34 PM
investigating
We are continuing to investigate this issue.
Jun 29, 9:34 PM
investigating
We are actively investigating this issue.
Jun 29, 9:32 PM
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
Started: Jun 29, 3:39 PM
investigating
We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Jun 29, 3:39 PM
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
Started: Jun 29, 3:39 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 29, 5:06 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 29, 4:47 PM
investigating
We are continuing to investigate this issue.
Jun 29, 4:10 PM
investigating
We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Jun 29, 3:39 PM
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
Started: Jun 29, 3:30 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 29, 6:23 PM
identified
We continue to work to implement a fix for the issue.
Jun 29, 5:51 PM
identified
The issue has been identified and we continue our work to implement a fix.
Jun 29, 5:16 PM
identified
We have identified the issue and a fix is being implemented.
Jun 29, 5:07 PM
investigating
We are continuing to investigate this issue.
Jun 29, 5:05 PM
investigating
We are actively investigating this issue.
Jun 29, 3:30 PM
Intermittent Errors and Delays (Incident 5219)
Started: Jun 28, 6:49 AM
identified
We have identified the issue and a fix is being implemented.
Jun 28, 6:58 AM
investigating
We are actively investigating this issue.
Jun 28, 6:49 AM
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190) (Incident 5209)
Started: Jun 26, 6:06 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 26, 7:02 PM
identified
We have identified the issue and a fix is being implemented.
Jun 26, 6:06 PM
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190)
Started: Jun 25, 8:12 PM
identified
We have identified the issue and a fix is being implemented.
Jun 25, 8:57 PM
investigating
We are continuing to investigate this issue.
Jun 25, 8:36 PM
investigating
We are actively investigating this issue.
Jun 25, 8:12 PM
Platform Latency in UAT (Incident 5187)
Started: Jun 25, 8:44 AM
monitoring
Fix has been implemented and we are now monitoring telemetry to validate.
Jun 25, 10:27 AM
identified
We have identified the source of the issue and are preparing a fix.
Jun 25, 10:12 AM
investigating
Customers may be experiencing latency on the platform in the UAT Environment. Engineers have been engaged and are actively triaging this issue.
Jun 25, 8:44 AM
Users downloading archived document ZIP files may see missing official Docusign platform seals (Incident 5139)
Started: Jun 18, 10:43 PM
identified
The fix is still in progress and being deployed. We will provide an update upon resolution.
Jun 24, 1:15 PM
identified
An issue has been identified where documents downloaded via archived ZIP files with "masked fields" enabled are missing their Docusign platform seals. A fix is underway. We will provide an update upon resolution.
Target Fix Date: June 23, 2026
Temporary Workaround: Download documents individually rather than as an archived ZIP file to ensure platform seals are successfully applied.
Jun 18, 10:43 PM
Salesforce for Gen customers may be unable to generate documents (Incident 5132)
Started: Jun 17, 7:28 PM
monitoring
We continue to monitor the environment to ensure stability.
Jun 17, 10:58 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 17, 8:41 PM
investigating
We are actively investigating this issue.
Jun 17, 7:28 PM
Salesforce for Gen customers are unable to generate documents (Incident-5122)
Started: Jun 16, 4:52 PM
identified
We are continuing to work on a fix for this issue.
Jun 16, 10:01 PM
identified
We have identified the issue and a fix is being implemented.
Jun 16, 10:00 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 16, 8:46 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 16, 6:28 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 16, 5:59 PM
investigating
We are continuing to investigate this issue.
Jun 16, 4:54 PM
investigating
We are actively investigating this issue.
Jun 16, 4:52 PM
Customers may experience intermittent latency (Incident 5118)
Started: Jun 16, 8:37 AM
investigating
We continue to investigate the issue. Performance has improved but the issue is still under investigation.
Jun 16, 3:20 PM
investigating
We are continuing to investigate this issue.
Jun 16, 10:34 AM
investigating
We are actively investigating this issue.
Jun 16, 8:37 AM
Users may experience performance latency when utilizing the doc2pdf service (Incident 5085)
Started: Jun 15, 5:24 PM
identified
We are have identified the root cause and we are implementing a fix.
Jun 15, 5:24 PM
Email notifications sent from custom domains may not be delivered (Incident 5106)
Started: Jun 15, 2:00 PM
investigating
We are actively investigating the issue.
Jun 15, 2:00 PM
Notification failures when utilising Outlook (Incident 5087)
Started: Jun 12, 6:04 AM
monitoring
A fix has been applied and our engineering teams are actively reviewing our telemetry to confirm this fix has mitigated the issue.
Jun 12, 6:10 AM
investigating
Customers utilising Outlook may receive delivery notification failures when sending envelopes to signers. Engineering teams have been engaged and we are actively triaiging this issue.
Jun 12, 6:04 AM
Users may encounter errors when attempting to process envelopes (Incident 5072)
Started: Jun 11, 7:45 PM
investigating
We are investigating this issue.
Jun 11, 7:45 PM
Document Upload and Generation Errors (Incident 5073)
Started: Jun 11, 7:03 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 11, 10:13 PM
identified
We have identified the issue and a fix is being implemented.
Jun 11, 10:05 PM
investigating
We continue to investigate the issue.
Jun 11, 9:52 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 11, 8:34 PM
investigating
We continue to investigate the issue and additional resources have been engaged.
Jun 11, 8:19 PM
investigating
We are continuing to investigate this issue.
Jun 11, 7:49 PM
investigating
We are actively investigating this issue.
Jun 11, 7:03 PM
Customers Unable to Purchase Plans (Incident 5034)
Started: Jun 5, 10:02 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 5, 10:22 PM
identified
We have identified the issue and a fix is being implemented.
Jun 5, 10:15 PM
investigating
We are actively investigating this issue.
Jun 5, 10:02 PM
Organization Reports May Remain in "Exporting" Status (Incident 5020)
Started: Jun 4, 6:58 AM
identified
We are continuing to work on a fix for the issue.
Jun 4, 9:07 AM
identified
Customers may be experiencing issues when attempting to export organization reports. Our engineering teams are engaged and have identified the cause and are working on a fix for this.
Jun 4, 6:58 AM
Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003)
Started: Jun 2, 11:32 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 2, 11:56 PM
identified
The issue has been identified and a fix is being implemented.
Jun 2, 11:50 PM
investigating
We are currently investigating this issue.
Jun 2, 11:32 PM
May 2026
Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968)
Started: May 28, 2:51 PM
identified
Engineers have identified the root cause and are executing a fix.
May 28, 3:50 PM
identified
Customers attempting to send an envelope or use SMS/Phone Authentication for Envelopes utilising a +86 will experience errors during this process. Engineering teams have been engaged and triage is underway.
May 28, 2:51 PM
Customers may experience timeouts related to core AI features which include document summarization and extractions. (incident 4961)
Started: May 27, 1:04 AM
monitoring
We are continuing to monitor for any further issues.
May 28, 12:05 AM
monitoring
We are continuing to monitor for any further issues.
May 27, 10:04 PM
monitoring
We are continuing to monitor for any further issues.
May 27, 9:16 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 27, 7:30 PM
identified
We are continuing to work on a fix for this issue.
May 27, 5:24 PM
identified
The issue has been identified and a fix is being implemented.
May 27, 4:03 AM
investigating
We are continuing to investigate this issue.
May 27, 3:32 AM
identified
The issue has been identified and a fix is being implemented.
May 27, 2:35 AM
investigating
We are currently investigating this issue.
May 27, 1:04 AM
Salesforce is experiencing an outage that may impact customers using the Salesforce integration (Incident-4935)
Started: May 21, 11:12 PM
investigating
Salesforce is experiencing an outage that may impact customers using the Salesforce integration. Docusign services are not experiencing any outages at this time. The issue will resolve when Salesforce resolves their outage.
May 21, 11:12 PM
Some customers may experience latencies sending and signing in EU (Incident-4915)
Started: May 19, 12:59 PM
investigating
We are continuing to investigate the issue.
May 19, 1:30 PM
investigating
We are currently investigating the issue.
May 19, 12:59 PM
Some customers may experience latencies sending and signing in NA1 and NA3 (Incident-4902)
Started: May 18, 5:55 PM
investigating
We are currently investigating this issue.
May 18, 5:55 PM
Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863)
Started: May 14, 6:45 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 14, 7:54 PM
identified
The issue has been identified and a fix is being implemented.
May 14, 7:23 PM
investigating
We are currently investigating this issue.
May 14, 6:45 PM
Workflow Reports Experiencing Timeout Errors (Incident 4874)
Started: May 13, 11:49 AM
monitoring
A fix has been implemented and we are observing telemetry to validate.
May 13, 1:41 PM
identified
We are continuing to work on a fix for this issue.
May 13, 11:50 AM
identified
Customers may be experiencing timeout errors with Workflow and Document Reports. Engineering teams have been engaged and the issue has been identified, a fix is currently being implemented.
May 13, 11:49 AM
Customers may experience issues accessing PowerForms (Incident-4870)
Started: May 12, 7:41 PM
investigating
We are currently investigating this issue.
May 12, 7:41 PM
Users may experience timeouts when attempting to complete document transactions (incident 4866)
Started: May 12, 6:17 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 12, 7:51 PM
identified
We are continuing to work on a fix for this issue.
May 12, 7:33 PM
identified
The issue has been identified and a fix is being implemented.
May 12, 6:43 PM
investigating
We are currently investigating this issue.
May 12, 6:17 PM
Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)
Started: May 12, 1:42 PM
monitoring
A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.
May 12, 3:55 PM
identified
Additional Engineering teams have been engaged to triage this issue, the current workaround is still functional:
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve this issue.
May 12, 3:20 PM
monitoring
Our engineering teams have deployed a fix and we are now monitoring to validate.
May 12, 2:24 PM
identified
We are continuing to work on a fix for this issue.
May 12, 2:23 PM
identified
We are currently investigating an issue where a subset of customers utilising a particular firewall may experience issues when attempting to switch to CLM.
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve ...
May 12, 1:42 PM
Users may experience connection errors when trying to switch to CLM (Incident 4861)
Started: May 12, 8:46 AM
investigating
Additional teams have been engaged to triage this issue.
May 12, 9:45 AM
investigating
A subset of customers may be experiencing connection errors in the UI when attempting to switch to CLM. Engineering teams have been engaged and are actively triaging this issue.
May 12, 8:46 AM
Users may encounter errors that will prevent document uploading or envelope creation (Incident 4860)
Started: May 11, 11:14 PM
identified
The issue has been identified and a fix is being implemented.
May 11, 11:14 PM
AU Site Outage (Incident 4840)
Started: May 8, 2:09 AM
monitoring
We have implemented a mitigation and are monitoring the results.
May 8, 3:03 AM
investigating
We are continuing to investigate this issue.
May 8, 2:35 AM
investigating
We are currently investigating this issue.
May 8, 2:09 AM
April 2026
Send Latency in EU (Incident 4776)
Started: Apr 28, 9:03 AM
identified
Engineers have identified a root cause and are working on releasing a fix.
Apr 28, 9:24 AM
investigating
A subset of customers in EU may experience latency with Send operations. Engineering teams have been engaged and are actively triaging.
Apr 28, 9:03 AM
Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752)
Started: Apr 23, 8:14 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 8:27 PM
investigating
We are currently investigating this issue.
Apr 23, 8:14 PM
Some users might experience latency when attempting to convert non-PDF documents (Incident-4750)
Started: Apr 23, 4:28 PM
monitoring
We continue to monitor for stability while we investigate possible secondary factors.
Apr 23, 10:34 PM
monitoring
We are continuing to monitor for any further issues.
Apr 23, 9:23 PM
monitoring
We are continuing to monitor for any further issues.
Apr 23, 8:02 PM
monitoring
We continue to monitor the environment to ensure stability.
Apr 23, 7:18 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 23, 5:31 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 5:07 PM
investigating
We are currently investigating this issue.
Apr 23, 4:28 PM
Customers may experience intermittent latency and errors in Navigator (Incident 4748)
Started: Apr 23, 3:27 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 9:21 PM
investigating
We are continuing to investigate this issue.
Apr 23, 7:37 PM
investigating
We are continuing to investigate this issue.
Apr 23, 6:35 PM
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
Apr 23, 5:40 PM
investigating
We are continuing to investigate this issue.
Apr 23, 4:44 PM
investigating
We are currently investigating the issue.
Apr 23, 3:27 PM
Login failures and Latency Issues with Sending and Signing Envelopes
Started: Apr 17, 2:47 PM
monitoring
We are continuing to monitor for any further issues.
Apr 17, 3:57 PM
monitoring
Internal testing is showing the implemented fix has resolved the impact, we are continuing to monitor to ensure the issue is fully mitigated.
Apr 17, 3:12 PM
identified
Our engineering teams have identified the root cause of this issue and are in the process of deploying a fix.
Apr 17, 2:53 PM
investigating
We are currently investigating a spike in latency for send and sign services which may affect a subset of customers. We have engaged our engineering teams and are actively triaging this issue.
Apr 17, 2:47 PM
Intermittent Errors in UAT (Incident 4682)
Started: Apr 11, 3:54 AM
identified
The issue has been identified and a fix is being implemented.
Apr 11, 4:41 AM
investigating
We are continuing to investigate this issue.
Apr 11, 4:19 AM
investigating
Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.
Apr 11, 3:54 AM
User Membership Group Update Delays (Incident 4672)
Started: Apr 9, 7:40 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 9, 9:01 PM
identified
We are implementing a change to resolve the AU delay.
Apr 9, 8:39 PM
identified
NA1 is now back to normal operational expectations. We are working to resolve the issue in AU now.
Apr 9, 7:56 PM
identified
Changes to user membership groups is significantly delayed. We are making changes to reduce or remove the delay.
Apr 9, 7:40 PM
March 2026
Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)
Started: Mar 27, 12:41 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 27, 10:39 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 9:00 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 5:22 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 4:21 PM
identified
Engineers are continuing to triage and develop a fix to the identified issue.
Mar 27, 3:42 PM
identified
A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix.
Mar 27, 2:59 PM
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
Mar 27, 2:26 PM
investigating
Due to a recently identified issue in our UAT environments, tasks may be routed incorrectly, leading to failures. Our team is actively working on identifying the root cause and mitigating it, and we will keep you updated as progress is made. Please note that any workflows and tasks on your Production environment should not be affected, and will still be executed normally.
Mar 27, 12:41 PM
Search Indexing Delays (Incident 4539)
Started: Mar 18, 12:13 AM
identified
As a continuation of incident 4517, a subset of customers may experience incomplete search results for historical documents older than one year. A fix is currently underway, and full resolution is anticipated by Wednesday, March 18, 2026 at 11:00 AM UTC.
Mar 18, 12:13 AM
CLM & Salesforce Integration Customers may be having difficulties accessing EU sites (Incident 4517)
Started: Mar 14, 4:54 PM
monitoring
We continue to monitor the environment to ensure stability.
Any company logos that were missing or outdated have been updated.
Mar 17, 7:40 PM
monitoring
We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
Mar 17, 4:36 AM
monitoring
A fix has been implemented and we are monitoring the results.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
Mar 17, 12:51 AM
identified
The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.
Mar 16, 10:03 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 7:25 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 5:19 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 3:15 PM
identified
We are still continuing to work through the failover steps for EU21.
Mar 16, 12:49 PM
identified
We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.
Mar 16, 11:12 AM
identified
We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.
Mar 16, 11:03 AM
identified
We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.
Mar 16, 10:46 AM
identified
We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.
Mar 16, 9:32 AM
identified
We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.
Mar 16, 8:58 AM
identified
We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.
Mar 16, 8:27 AM
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
Mar 16, 6:59 AM
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
Mar 16, 4:49 AM
identified
We have identified an intermittent degradation in our EU11 environment and are working on fixing it.
Mar 16, 3:31 AM
identified
We are continuing to work through failover steps.
Mar 16, 2:47 AM
identified
We are continuing to work through failover steps.
Mar 16, 12:51 AM
identified
We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.
Mar 15, 11:25 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 10:31 PM
identified
The issue has been identified and a fix is being implemented.
Mar 15, 8:00 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 5:17 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 11:40 AM
identified
The issue has been identified and a fix is being implemented.
Mar 15, 8:30 AM
monitoring
We are continuing to monitor for any further issues.
Mar 15, 4:23 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 14, 11:41 PM
identified
We are continuing to remediate impact to EU21 customers.
Mar 14, 11:11 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 10:09 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 8:24 PM
identified
We are continuing to remediate impact to EU11 and EU21 customers.
Mar 14, 6:27 PM
identified
We are continuing to work on a fix for EU21 customers. EU21 customers may observe issues accessing the site. EU11 customers may see intermittent issues generating documents.
Mar 14, 4:58 PM
monitoring
A fix has been implemented for US sites as of approximately 09:00 UTC.
Mar 14, 4:54 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 3:59 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 2:44 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 9:19 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 9:17 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 6:07 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 3:11 AM
identified
The issue has been identified and a fix is being implemented.
Mar 14, 2:42 AM
investigating
We are continuing to investigate this issue.
Mar 14, 2:27 AM
investigating
We are continuing to investigate this issue.
Mar 14, 2:08 AM
investigating
We are currently investigating this issue.
Mar 14, 2:07 AM
Users may encounter errors while attempting to upload or edit documents. (Incident 4504)
Started: Mar 12, 8:23 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 12, 9:41 PM
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
Mar 12, 8:49 PM
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
Mar 12, 8:23 PM
identified
The issue has been identified and a fix is being implemented.
Mar 12, 7:23 PM
investigating
We are currently investigating this issue.
Mar 12, 6:15 PM