WorkRampworkramp.com site error
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 17:54 UTC and 20:22 UTC, some customers in the US and EU region may have experienced various irregularities for data availability and alert notifications. Impacted services have returned to normal operations, following the recovery of our dependent cloud provider systems.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
🛠 We have resolved all known issues causing the Twitch website to fail to load for some users.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.
Resolved
At 4:37AM PST, Keeper experienced API errors in the EU region. Service was restored by 5:35AM PST following a database failover. The issue was caused by a bug in the new Device Management API, released the day before. During device registration, the system attempted to delete old devices, which created high database load for accounts with large device counts. The bug was identified, fixed, and a patch was deployed. We apologize for the disruption. To ensure uninterrupted access, we recommend enabling “Work Offline” mode for your account.
Resolved
Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.
Resolved
Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.
Resolved
Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.
Resolved
Some Llama 3.3-70B prompts contained corrupt responses. We restored normal service performance at 1 AM PST on June 9th.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
On `2025-05-13` We experienced an outage affecting the Bitly Public API from `18:12Z` to `18:34Z`. This affected the ability to use the Bitly site or create new links, but did not impact usage of any existing links. The root cause was an error with a newly provisioned application secret which caused a fatal API service error that didn't fail our deployment pipeline. Our monitoring systems detected the issue quickly and we successfully rolled back to restore services. We have since taken steps towards resolving root causes, including improving secrets validation and faster failure detection during service initialization.
Resolved
This incident has been resolved.
Resolved
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
Resolved
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
Resolved
We are marking this incident as resolved. Please reach out to support@crusoecloud.com if you experience any issues.
Resolved
Between 21:39 UTC on June 09, 2025 and 21:35 UTC on June 10, 2025, we experienced a forge invocation errors impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. The issue has now been resolved and the service is operating normally. We are actively monitoring this capability.
Resolved
Admins receiving a "Sorry, an error occurred" message when working in the Admin console.
Resolved
This incident has been resolved.
Resolved
Issues affecting the NGC services have been resolved and the service is operating normally.
Resolved
The incident has been resolved and we will continue to monitor the situation closely to prevent further service impact.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
A configuration change was made to the Content Distribution Network that caused the web clients to lose access to files that were needed for startup. The web app couldn't be loaded between 1:48 PM and 2:16 PM PDT. Impact was limited to users who tried to start the app between those times.
Resolved
The issue with candidate texting in Lever has been resolved. The incident occurred from Jun 9th 12 pm until Jun 9th 1:30 pm. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
Resolved
The issue has been resolved. The processing of the backlog is progressing, and all delayed logs will be available shortly
Resolved