Jamf (Apple Management)
September 27, 11:18am
Networking & Systems
Jamf (Apple Management)
Sep-27, 11:18am
We have identified an issue related to missing packages in JCDS for a small number of instances. If you believe you are impacted by this outage, you can remediate by re-enabling your Cloud Service Connection. It may take up to 1 hour for packages to be available after this step is completed. https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/Cloud_Services_Connection.html
We are actively working on a non-user initiated fix for this issue. Additional details will be provided by 1900  UTC Friday September 27, 2024.
Sep-27, 12:51pm
We are in the process of deploying a non-user initiated fix for this issue. We anticipate that all impacted instances will have their JCDS access restored by 2000 UTC Friday September 27, 2024.
Sep-27, 2:57pm
This incident has been resolved and connectivity to JCDS packages have been restored.
August 06, 3:17pm
Networking & Systems
Jamf (Apple Management)
Aug-6, 3:17pm
Details: Customers may not be able to access JCDS files that were uploaded prior to an internal Jamf system change on 5 August 2024. All customer assets will be restored shortly.
Current Actions: Jamf is currently working on a fix to restore access to packages, apps, and books to customers who are experiencing this issue.
Impact: Packages, apps, and books that were stored in JCDS will not be able to be deployed to end user devices until resolved.
Status: Ongoing
Estimated resolution: 2359 UTC Tuesday, August 6, 2024
Aug-6, 4:37pm
The JCDS is now operational and access to files in the JCDS has been restored. We apologize for any inconvenience this has outage may have caused.
June 28, 9:57pm
Networking & Systems
Jamf (Apple Management)
Jun-28, 9:57pm
Currently we are monitoring an ongoing JCDS issue, affecting the AMER region that is preventing usage. The fix has been implemented and is propagating here soon.
Jun-28, 11:22pm
Currently we are monitoring an ongoing JCDS issue. The fix has been implemented and we are awaiting for the propagation to apply.
We will continue to keep this page upadted with new information.
Jun-28, 11:32pm
The fix has been applied and now been propogated to all services.
We apologize for the inconvenience caused.
March 12, 12:04pm
Networking & Systems
Jamf (Apple Management)
Mar-12, 12:04pm
An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes. Currently this seems to be related to communication with APNS.
Mar-12, 12:17pm
Details: We’re currently addressing an issue marked by a 503 error, affecting access to our platform. Technical challenges are impacting our ability to process requests.
Current Actions: Our engineering team is actively working on identifying and resolving the issue. We’re analyzing system logs and performance to quickly restore service.
Impact:.Users may experience an inability to login and may see failures around self-service connections and enrollments.
Status: Ongoing. We’re dedicated to minimizing disruption and restoring full functionality.
We appreciate your patience and are committed to resolving this as swiftly as possible
Mar-12, 2:58pm
Service Update
We are continuing to work diligently to resolve the service interruptions currently impacting our customers. Our team is fully engaged and focused on rectifying the issue as swiftly as possible.
Ongoing Actions:
Our investigation is still in progress, with all efforts aimed at identifying and implementing a solution promptly. We have mobilized additional resources to ensure a rapid resolution.
Staying Informed:
We are committed to providing you with the latest updates as our work progresses. Another update will be provided in about 2 hours.
Thank you for your continued patience and understanding.
Mar-12, 5:21pm
Issue Status: Ongoing
Update: It’s been over two hours since we first reported the service interruption caused by a 503 error. Our engineering team is fully committed to resolving the underlying issues.
Current Efforts: Analysis of system logs and performance metrics is ongoing, with our team working tirelessly to find and implement a fix. Progress is being made, though the issue remains unresolved.
Impact Reminder: Users may still experience difficulties accessing our services. We are aware of the inconvenience this causes and are focused on restoring normal operations as quickly as possible.
Next Steps: We are continuing to pursue all avenues to speed up the recovery process and will provide updates as soon as new information becomes available.
Thank you for your continued patience and understanding. Our team is dedicated to resolving this issue as swiftly as possible.
Mar-12, 7:20pm
We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it.
Here's a brief overview of the current situation:
Issue Status: The service interruption caused by a 503 error is ongoing.
Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time.
Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible.
Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments.
Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.
Mar-12, 9:51pm
We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it.
Here's a brief overview of the current situation:
Issue Status: There is a small amount of services have an interruption which was caused by a 503 error.
Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time.
Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible.
Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments.
Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.
Mar-13, 3:25am
We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it.
Here's a brief overview of the current situation:
Issue Status: There is a small amount of services have an interruption which was caused by a 503 error.
Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time.
Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible.
Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments.
Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.
Mar-13, 7:45am
We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it.
Here's a brief overview of the current situation:
Issue Status: There is a small amount of services have an interruption which was caused by a 503 error.
Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time.
Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible.
Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments.
Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.
Mar-13, 12:15pm
We are continuing to address a performance issue affecting some of our services. Our technical teams are actively working on measures to ensure system stability and are closely monitoring the situation. We are dedicated to minimizing any impact on our customers and are making progress toward a resolution.
Further updates will be shared as they become available. We appreciate your continued patience and understanding.
Mar-13, 2:28pm
We are continuing to investigate this issue.
Mar-13, 3:39pm
We’ve identified a potential root cause for a recent issue and are actively working to resolve it.
We appreciate your patience and will provide further updates as soon as possible.
Mar-13, 7:37pm
We’ve identified a potential root cause for a recent issue and are actively working on a solution in order to resolve it.
We appreciate your patience and will provide further updates as soon as possible.
Mar-14, 3:51am
We are continuing to work on a fix for this issue.
Mar-17, 7:24pm
We’re happy to announce a hotfix is now available for the issues reported. Our team has worked hard to ensure your operations can continue smoothly.
Please be aware, continued outages could be due to not updating to the version with the hotfix.
To resolve these issues, we urge all customers to upgrade immediately.
We appreciate your prompt action on this and thank you for your ongoing support.
Mar-18, 7:24pm
auto-closed
February 23, 1:20am
Networking & Systems
Jamf (Apple Management)
Feb-23, 1:20am
We are currently investigating this issue.
Feb-23, 1:46am
The issue has been identified and a fix is being implemented.
Feb-23, 1:46am
A fix has been implemented and we are monitoring the results.
February 11, 4:50pm
Networking & Systems
Jamf (Apple Management)
Feb-11, 4:50pm
An issue has been identified that is affecting some Jamf Pro Premium Cloud customers hosted in the us-east-1 region. We are working to resolve and will provide next update in 45 minutes.
Feb-11, 4:50pm
We are continuing to investigate this issue.
Feb-11, 6:46pm
We are continuing to investigate this issue.
Feb-11, 8:14pm
We are continuing to investigate this issue that is affecting some Jamf Pro Premium Cloud customers hosted in the us-east-1 region. We will provide an update ASAP.
Feb-12, 7:47am
We are continuing to investigate this issue.
Feb-12, 9:32am
We have finished the investigation and the remediation of the issue. At this time we will continue to monitor the situation, thank you for everyone's patience and we apologize for any disruptions this might have caused.
Feb-12, 4:29pm
This incident has been resolved.
January 30, 8:33pm
Networking & Systems
Jamf (Apple Management)
Jan-30, 8:33pm
An issue has been identified affecting Jamf Pro Cloud:
- instance creations, updates, and deletes may fail
- some instances may see SSL errors
Engineers have identified the issue and are working to resolve it as soon as possible
Jan-31, 6:17am
We are continuing to work on a resolution for this issue.
Feb-1, 5:39am
We continue to work towards a resolution of this issue.
Feb-1, 10:41am
We have a team dedicated to finding the root source of the issue. We are close to identifying the source and will implement a fix as soon as possible. We apologize for the inconvenience this caused over the last few days.
Feb-1, 3:01pm
Our team is actively working to resolve the issue and restore normal service as quickly as possible. We apologize for the inconvenience.
Feb-1, 4:46pm
Our team is actively working to resolve the issue and restore normal service as quickly as possible. We have completed ap-northeast-1, we will update this thread as regions complete. We apologize for the inconvenience.
Feb-2, 1:35am
While we continue to work to resolve this issue, we also have identified a small number of instances that may be temporarily unavailable in the regions marked as "partial outage"
Feb-2, 12:31pm
We understand the critical role our cloud services play in your operations and sincerely apologize for the current inconvenience. Please be assured that we are fully committed to swiftly resolving this issue by deploying all necessary resources. Thank you for your understanding and patience.
Feb-2, 4:38pm
We recognize the significant impact this outage may have on your operations and sincerely apologize for the inconvenience. Please be assured that our team is fully committed and working tirelessly to resolve this issue promptly. We anticipate the current disruptions may continue well into the weekend, but we are making every effort to restore services to full capacity as quickly as possible. Your understanding and patience are greatly appreciated during this time.
Feb-3, 11:36am
We have completed ap-southeast-2, eu-central-1, eu-west-2, us-east-1 regions. We are continuing to resolve issues in us-west-2, ap-northeast-1. Thank you for your patience.
Feb-4, 4:44pm
We are continuing to work on a fix for this issue.
Feb-4, 8:33pm
We have completed applying the fix in the ap-southeast-2 region. We are continuing to resolve issues in us-west-2, ap-northeast-1. Thank you for your patience.
Feb-5, 12:42am
We have completed applying the fix in the ap-northeast-1 and us-west-2 regions. We are continuing to monitor for additional issues. Thank you for your patience.
Feb-6, 4:45pm
The incident affecting our cloud servers has been successfully resolved. We have conducted a thorough review of our systems and will be conducting an internal investigation of the incident. We understand the importance of our cloud services to your business operations, and we apologize again for any inconvenience this incident may have caused.
December 06, 3:27pm
Networking & Systems
Jamf (Apple Management)
Dec-6, 3:27pm
We are currently investigating this issue.
Dec-6, 3:57pm
This incident has been resolved.
December 06, 11:05am
Networking & Systems
Jamf (Apple Management)
Dec-6, 11:05am
We are currently investigating this issue.
Dec-6, 11:54am
We are continuing to investigate this issue.
Dec-6, 12:02pm
This incident has been resolved.
September 05, 12:49pm
Networking & Systems
Jamf (Apple Management)
Sep-5, 12:49pm
An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.
Sep-5, 1:13pm
An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.
Sep-5, 1:59pm
We continue working on the issue, and most instances have been resolved. We will provide an update in 30 minutes.
Sep-5, 2:35pm
We are continuing to implement the fix. We will provide an update in 45 minutes.
Sep-5, 3:22pm
We are continuing to work through the issue. We are making progress we greatly apologize for any inconvenience this might have caused.
Sep-5, 3:30pm
We are continuing to work on a fix for this issue.
Sep-5, 3:36pm
- Premium instances were unaffected during this outage, and were incorrectly identified as a part of this outage. Apologize for the confusion.
- EUW2(London) back online
- Remaining instances are coming online slowly with partial customer outages(<500) impacted currently spread over 5 regions, USE1, EUC1, USW2, APNE1, APSE2
Sep-5, 3:37pm
A fix has been implemented and we are monitoring the results.
Sep-5, 4:43pm
A one-time investigative query was run today against all database servers, the query was vetted for impact although some larger datasets weren't accounted for. This resulted in a large number of instances experiencing a service outage. We are truly sorry for the disruption this has caused.
No incidents in range