14 Scratchpad incidents · novembre 2019 — official updates, affected components, duration and resolution details.
Scratchpad is experiencing an intermittent disruption caused by an AWS outage. We know how disruptive this is and we're truly sorry. Our team is treating this as a top priority and working to restore services for impacted users as quickly as possible. Thank you for your understanding.
This incident has been resolved.
Scratchpad is currently impacted by an intermittent Salesforce outage. We know how disruptive this is, and we're truly sorry. While the issue stems from Salesforce, our team is treating this as a top priority and working to restore service for affected customers as quickly as possible.
Salesforce infrastructure seems to have resolved. We're monitoring in case it reoccurs. We're sorry for any disruptions.
We are currently seeing issues with our infrastructure provider Cloudflare that is causing our server to not respond. We're looking into a workaround while they fix this issue. You can follow their updates here: https://www.cloudflarestatus.com/ We're sorry for the inconvenience and will be posting updates as we learn more.
The site is back up. We're monitoring to see if this happens again.
This incident has been resolved.
We are experiencing a disruption of service due to a global outage with our DNS provider. Our team is monitoring the situation as a top priority and working hard to bring the Scratchpad service back online.
This incident has been resolved.
We are experiencing an outage due to to a global outage with our hosting provider. We are closely monitoring the situation, and will post regular updates.
All services have been restored
This incident has been resolved.
We're experiencing intermittent timeouts where the application won't load. We're looking into the root cause. We apologize for the inconvenience.
This incident has been resolved.
We're still seeing sporadic degraded performance across Salesforce apis for certain tenants. You may experience slow load times or data not loading. We're monitoring the APIs and will update you as we learn more. Our apologies for the inconvenience.
This incident has been resolved.
Some users may be experiencing problems connecting to Salesforce.
This incident has been resolved.
We're currently investigating an issue with Salesforce api performance degradation. We're looking to see if there is anything we can do on our end to alleviate the problem.
We are continuing to investigate this issue.
Salesforce apis appear to be back to normal and Scratchpad should be functioning correctly now. We'll keep monitoring the situation.
We are currently investigating an issue where Command J crashes the current tab you are on.
We are continuing to investigate this issue.
This incident has been resolved.
We're actively investigating slow response times across the app.
We are continuing to investigate this issue.
A background process slowed our database down for ten minutes. Performance should be back to normal and we will look into how to prevent this in the future.
We're currently investigating an issue where when typing in notes the cursor jumps to another spot in the note.
We've released a fix for the cursor jumping issue. Please update to the latest version of Scratchpad to get the fix. You can do this here: https://help.scratchpad.com/en/articles/2766166-updating-to-the-latest-version-of-scratchpad Or email us for help: [email protected] We're sorry for the disruption. Thank you.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Our infrastructure provider had a brief outage of about five minutes. The issue appears to have been resolved. We're monitoring it.
This incident has been resolved.
Sorry! We're experiencing a temporary issue displaying your notes at the moment. The issue only impacts displaying the notes. Our team is working on this as top priority right now and it will be resolved soon.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This issue has been resolved. We're sorry for the inconvenience!
