Snaplogic 장애 기록

1. 2026년 7월 24일 PM 12:00 UTCinvestigating

   시작 시간: 4:00 오전 PST 몇 고객이 SnapLogic Platform UI에 로그인할 수 없습니다. 우리의 팀은 현재 조사입니다. 언제나, 어떤 특이한 행동을 경험한다면, 평소의 방식으로 지원해 주세요 ([email protected]) 이메일 [email protected] 으로 지원 팀과 함께 지원 티켓을 열 수 있습니다. 다음 업데이트: 7월 24일 6:00 오전 PST

2. 2026년 7월 24일 PM 12:42 UTCmonitoring

   상태: 감시 상태 업데이트: 모든 서비스는 정상적인 성능 임계 값 내에서 운영되며 검증은 안정적인 작동을 확인합니다. 어떤 문제라도 경험할 경우, 지속적인 분석의 일부로 검토할 수 있도록 지원해 주세요. 다음 업데이트 : 09 : 00AM PST

3. 2026년 7월 24일 PM 5:26 UTCresolved

   제품 설명 상태: 해결 종료 시간: 4:15 오전 PST 자주 묻는 질문 모니터링은 영향을받는 범위의 안정적인 작동을 확인합니다. 운영 검토가 필요한 고객은 지원과 직접 협조할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 17일 PM 5:02 UTCinvestigating

   Start time: April 17th 3:15 AM PST We are currently investigating latency in pipeline preparation and execution time for a few customers that is occurring on the SnapLogic platform in the US region. Our team is investigating this behavior with the highest priority, dedicating all resources to resolve the issue as quickly as possible. We will update this incident with our progress. Please open a support ticket with our Support team by emailing [email protected] with any questions or concerns. Next update: April 17th 12:00 PM PST

2. 2026년 4월 17일 PM 6:23 UTCinvestigating

   Start time: April 17th 3:15 AM PST We are currently investigating latency in pipeline preparation and execution time for a few customers that is occurring on the SnapLogic platform in the US region. Our team is currently on a bridge and has identified several remediation options. We are testing all available options before moving forward with performing any changes. Please open a support ticket with our Support team by emailing [email protected] with any questions or concerns. Next update: April 17th 12:00 PM PST

3. 2026년 4월 17일 PM 6:57 UTCmonitoring

   Status: Monitoring Last Updated: 11:23 AM PST We have implemented remediation steps to address the pipeline preparation issues. Performance indicators are trending toward baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability. Next update by 1:00 PM PST

4. 2026년 4월 17일 PM 8:15 UTCresolved

   Resolved Status: Resolved End Time: 11:30 AM PST Performance has returned to expected baseline levels.Monitoring confirms stable operation across the affected scope. We will maintain elevated observation as a precautionary measure. Customers requiring operational review may coordinate directly with support.

1. 2026년 4월 15일 PM 12:09 UTCinvestigating

   Start time: 3:15 AM PST We are currently investigating latency in pipeline preparation and execution time for a few customers that is occurring on the SnapLogic platform in the US region. Our team is investigating this behavior with the highest priority and will update this incident with our progress. Please open a support ticket with our Support team by emailing [email protected] with any questions or concerns. Next update: April 15th 6:00 AM PST

2. 2026년 4월 15일 PM 1:12 UTCinvestigating

   Status: Investigating Start time: 3:15 AM PST Investigation continues impacting a subset of customers with pipeline preparation in the US region. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns. Next update: April 15th 8:00 AM PST

3. 2026년 4월 15일 PM 2:12 UTCmonitoring

   Status: Monitoring. Last Updated: 7:15 AM PST We implemented remediation steps to address pipeline preparation in the US region for a subset of customers. Performance indicators are trending toward baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability. Next update by 12:00 PM PST.

4. 2026년 4월 15일 PM 8:06 UTCresolved

   Status: Resolved End Time: 6:36 AM PST Performance has returned to expected baseline levels.Monitoring confirms stable operation across the affected scope. We will maintain elevated observation as a precautionary measure. Customers requiring operational review may coordinate directly with support.

1. 2026년 3월 2일 PM 2:21 UTCinvestigating

   Status: Investigating Start Time: 6:10AM PST We are investigating an issue affecting the Logging in to the US region. Customers may experience elevated latency or intermittent processing delays. Next update by: 7:30AM PST

2. 2026년 3월 2일 PM 2:39 UTCmonitoring

   Mitigation Update: Status: Monitoring Remediation steps have been implemented to address performance degradation in US region. We have achieved recovery and performance indicators are trending toward baseline levels with no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability, and will investigate the root cause upon full recovery. Next update by 7:30 AM PST.

3. 2026년 3월 2일 PM 6:04 UTCmonitoring

   Mitigation Update: Status: Monitoring Remediation steps have been implemented to address performance degradation in US region. Performance indicators are trending toward baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability. Next update by 1:00 PM PST.

4. 2026년 3월 2일 PM 9:04 UTCmonitoring

   Mitigation Update: Status: Monitoring Remediation steps have been implemented to address the performance degradation in the US region. Performance indicators are trending toward baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability. Next update by 3:00 PM PST.

5. 2026년 3월 3일 AM 1:52 UTCmonitoring

   Mitigation Update: Status: Monitoring Remediation steps have been implemented to address the performance degradation in the US region. Performance indicators are trending toward baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability.

6. 2026년 3월 3일 AM 5:01 UTCmonitoring

   Mitigation Update: Status: Monitoring Remediation steps have been implemented to address the performance degradation in the US region. Performance indicators are at baseline levels, and no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability.

7. 2026년 3월 3일 PM 2:13 UTCmonitoring

   Status: Investigating Start Time: March 3rd - 6:00AM PST We are investigating an issue affecting the Logging in and API calls to the US region Customers may experience elevated latency or intermittent processing delays. Next update by: 7:30AM PST

8. 2026년 3월 3일 PM 3:08 UTCinvestigating

   Status: Investigating Start Time: March 3rd - 6:00AM PST We sincerely apologize for the ongoing issues and any inconvenience they may have caused. Our team is actively working to resolve the situation as quickly as possible. We fully understand your concerns about stability and want to assure you that we’ve been carefully addressing the recent issues to ensure the platform is completely restored and operating smoothly again. Next update by 8:30 AM PST.

9. 2026년 3월 3일 PM 4:37 UTCmonitoring

   Recovery in Progress Status: Monitoring We have identified an API contributing to elevated traffic during peak periods, which led to disruption of certain production workloads in the US region. Remediation actions have been implemented to mitigate the impact. The SnapLogic platform is currently stable and performance metrics are trending back toward established baselines. A permanent patch is in development and will be deployed shortly. We are also evaluating additional safeguards to further strengthen platform resilience. Recovery progress continues to be validated against standard performance baselines. Further updates will be provided as improvements are completed. Next update by 9:30 PM PST.

10. 2026년 3월 3일 PM 8:21 UTCmonitoring

    Scheduled Rollback – March 3, 2026 To ensure continued platform stability, we will perform a rollback of the 4.44 release today: March 3, 2026 12:15 PM – 8:00 PM PST (8:15 PM GMT – 4:00 AM GMT) This rollback will be executed using a rolling restart methodology to preserve overall system availability. Scope: - All Snaplexes updated to v4.44 (February release) - Reverting to v4.43 GA (main-37094, November release) - North America-hosted Control Plane - Reverting from v4.44 to v4.43.2 (January release) What to Expect: - No impact for customers currently running Snaplex version 4.43.x - No planned downtime, except for customers with single-node Snaplexes (node restart required) - Actively running pipelines will complete prior to node restart - Temporary interruptions may occur for new pipeline executions during individual node restarts - Active user sessions will be logged out during restart and may immediately log back in Hourly progress updates will be provided. Next update by: 1:15PM PST

11. 2026년 3월 3일 PM 9:11 UTCmonitoring

    Scheduled Rollback – March 3, 2026 March 3, 2026 Started at 12:15 PM PST and is in Progress Status Update: The rollback to version 4.43 GA is progressing as planned. We have successfully downgraded 60% of Groundplexes with no issues identified. All nodes are restarting as expected, including those with active tasks. Once Groundplexes are complete, we will begin the rollback of Cloudplexes. Platform availability remains stable. What to Expect No impact for customers currently running Snaplex version 4.43.x No planned downtime, except for customers running single node snaplex on version 4.44.0.1 Actively running pipelines will complete prior to node restart Temporary interruptions may occur for new pipeline executions during individual node restarts Active user sessions will be logged out during restart and may immediately log back in Hourly progress updates will be provided.

12. 2026년 3월 3일 PM 10:16 UTCmonitoring

    Scheduled Rollback – March 3, 2026 March 3, 2026 Started at 12:15 PM PST and is in Progress Status Update: The rollback continues to proceed ahead of schedule. We have now successfully reverted 86% of Groundplexes to version 4.43 GA. System performance remains stable with no issues identified during the rolling restarts. What to Expect No impact for customers currently running Snaplex version 4.43.x No planned downtime, except for customers running single node snaplex on version 4.44.0.1 Actively running pipelines will complete prior to node restart Temporary interruptions may occur for new pipeline executions during individual node restarts Active user sessions will be logged out during restart and may immediately log back in Hourly progress updates will be provided.

13. 2026년 3월 3일 PM 11:13 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Status Update: The rollback is nearing completion for the data plane, with 90% of all nodes successfully reverted to version 4.43 GA. This includes 99% of Groundplexes and 81% of Cloudplexes. All systems remain stable as the final rolling restarts proceed, and we continue to see no impact on service availability What to Expect No impact for customers currently running Snaplex version 4.43.x No planned downtime, except for customers running single node snaplex on version 4.44.0.1 Actively running pipelines will complete prior to node restart Temporary interruptions may occur for new pipeline executions during individual node restarts Active user sessions will be logged out during restart and may immediately log back in Hourly progress updates will be provided.

14. 2026년 3월 4일 AM 12:19 UTCmonitoring

    Monitoring Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Status Update: A platform degradation was identified at 4:03 PM PST, but following immediate stabilization efforts and a database leader election, the system began recovering at 4:12 PM PST. The data plane rollback is nearly finished, with 96% of Cloudplexes and 98% of Groundplexes successfully reverted. We are proceeding with the final stages of the rollback. What to Expect No impact for customers currently running Snaplex version 4.43.x No planned downtime, except for customers running single node snaplex on version 4.44.0.1 Actively running pipelines will complete prior to node restart Temporary interruptions may occur for new pipeline executions during individual node restarts Active user sessions will be logged out during restart and may immediately log back in Hourly progress updates will be provided.

15. 2026년 3월 4일 AM 1:21 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Update : 5:20 PM PST Status Update: The platform has fully recovered from the connection-related degradation identified earlier this afternoon, and all systems are performing normally.  The data plane rollback is nearly finished, with 99% of Groundplexes and 96% of Cloudplexes successfully reverted to version 4.43 GA.  We began the control plane rollback at 5:15 PM PST, which is expected to take approximately 2 hours and 25 minutes. Upon login, customers may see a warning stating 'Snap Pack Catalog is deprecated.' This is an expected side effect of the version change and can be safely ignored as it does not impact operations. However, to prevent version mismatches and potential pipeline issues, please ensure any nodes still running version 4.44.x are manually restarted.  Support and CSM teams are currently reaching out to customers with pending restarts to assist with this process. Hourly progress updates will be provided.

16. 2026년 3월 4일 AM 2:21 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Update : 6:20 PM PST Status Update: The control plane rollback is currently in progress and proceeding without issue. However, due to unexpected latency with GitHub, a key component of our process, the rollback is running approximately 25 minutes slower than anticipated. As a result, the estimated completion time for the rollback has been moved from 7:40 PM PST to 8:05 PM PST. Please note that until the rollback is fully complete, the Snaplex label in the Monitor may still display "4.44." However, you can verify the rollback by checking the build number and version, which should correctly reflect the reverted version (main-37094) in Manager>>Snaplexes>>settings>>version Following the successful recovery from earlier today, we continue to see high completion rates for the data plane rollback. Support and CSM teams are actively working with the remaining customers who have not yet restarted their nodes to ensure they are successfully reverted to version 4.43 GA and to prevent any potential version mismatches Hourly progress updates will be provided.

17. 2026년 3월 4일 AM 3:19 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Update : 7:20 PM PST Status Update: The control plane rollback deployment encountered a timeout and failure due to the previously reported GitHub latency. This occurred just before the top of the hour, coinciding with a period of peak traffic on the control plane. To ensure a stable and successful transition, our engineering team elected to restart the deployment after the peak period concluded, and it was successfully re-initiated at 7:02 PM PST. This delay has further extended our estimated completion window. We now anticipate the full control plane rollback to be finalized by 9:45 PM PST. We continue to monitor all systems closely and will provide our next status update at the conclusion of the deployment Hourly progress updates will be provided.

18. 2026년 3월 4일 AM 4:17 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST and is in Progress Update : 8:20 PM PST Status Update: The control plane rollback deployment is proceeding steadily following its restart earlier this evening. Our engineering teams have not identified any further issues, and the deployment is currently on track to reach full completion by 9:45 PM PST. We will provide a final status update once the transition is finalized.

19. 2026년 3월 4일 AM 5:46 UTCmonitoring

    Scheduled Rollback – March 3, 2026 Started at 12:15 PM PST Completed at 9:30 PM PST The rollback is complete. All systems are now running on the targeted stable versions (Snaplex: main-37094 - 4.43 GA (Recommended); Control Plane: 4.43.2.0). We have transitioned to a 24/7 hands on monitoring phase to closely track traffic and performance patterns. This heightened surveillance will remain in place for the following weeks to guarantee long-term stability.

20. 2026년 3월 4일 PM 4:11 UTCinvestigating

    Production available but materially degraded Status: Investigating Start Time: 8:05AM PST We are investigating performance degradation affecting Log in and API calls in US region. Customers may experience elevated latency or intermittent processing delays. Next update by: 9:30AM PST

21. 2026년 3월 4일 PM 5:10 UTCmonitoring

    Mitigation Update: Status: Monitoring Last Updated: 9:10 AM PST Remediation steps have been implemented to address performance degradation in US region. We have achieved partial recovery and performance indicators are trending toward baseline levels with no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability, and will investigate the root cause upon full recovery. Next update by 10:30 AM PST.

22. 2026년 3월 4일 PM 6:42 UTCmonitoring

    Mitigation Update Status: Monitoring Last Updated: 10:10 AM PST Status Update: Platform performance has recovered and key indicators are trending back toward baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 12:00 AM PST

23. 2026년 3월 4일 PM 11:16 UTCmonitoring

    Mitigation Update Status: Monitoring Last Updated: 3:00 PM PST Status Update: Platform performance has recovered and key indicators back towards baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. This incident will remain open until a complete and verified resolution has been delivered.

24. 2026년 3월 5일 PM 2:10 UTCmonitoring

    Start Time: 6:00AM PST We are investigating an issue affecting the Logging in to the US region. Customers may experience elevated latency or intermittent processing delays. Next update by: 7:30AM PST

25. 2026년 3월 5일 PM 2:13 UTCinvestigating

    We are currently investigating this issue.

26. 2026년 3월 5일 PM 2:50 UTCmonitoring

    Mitigation Update Status: Monitoring Recovery Time: 6:45 AM PST Last Updated: 6:50 AM PST Status Update: Platform performance has recovered and key indicators back towards baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. This incident will remain open until a complete and verified resolution has been delivered. Next update by: 8 AM PST

27. 2026년 3월 5일 PM 4:01 UTCmonitoring

    Mitigation Update Status: Monitoring Status Update: Platform performance has been recovered and key indicators are trending back toward baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 11:00 AM PST

28. 2026년 3월 5일 PM 7:09 UTCmonitoring

    Status: Monitoring Status Update: Platform performance has recovered and key indicators are trending back toward baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. We will continue updating our progress toward resolving this intermittent issue on the SnapLogic US control plane within this trust incident. Platform degradation still causes intermittent disruption to our login UI and task execution. We performed several corrective actions that temporarily alleviated the issue. Once the issue is fully resolved, we will mark this incident as resolved. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 2:00 PM PST

29. 2026년 3월 5일 PM 10:08 UTCmonitoring

    Status: Monitoring Status Update: Platform performance has recovered and key indicators are trending back toward baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. We will continue updating our progress toward resolving this intermittent issue on the SnapLogic US control plane within this trust incident. Platform degradation still causes intermittent disruption to our login UI and task execution. We performed several corrective actions that temporarily alleviated the issue. Once the issue is fully resolved, we will mark this incident as resolved. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 5:00 PM PST

30. 2026년 3월 6일 AM 1:47 UTCmonitoring

    Status: Monitoring Status Update: Platform performance has recovered and key indicators are trending back toward baseline levels. Engineering teams remain actively engaged and are continuing to investigate intermittent spikes observed across different API calls. While the system is currently operating normally, we are maintaining heightened monitoring to ensure stability and identify the underlying cause. We understand the importance of reliable platform performance and appreciate your patience as we continue this investigation. We will have all hands on deck on Friday, March 6, from 5:00 a.m. to 7:00 a.m. PST. We will continue updating our progress toward resolving this intermittent issue on the SnapLogic US control plane within this trust incident. Platform degradation still causes intermittent disruption to our login UI and task execution. We performed several corrective actions that temporarily alleviated the issue. Once the issue is fully resolved, we will mark this incident as resolved. Next update: March 6 6:15 AM PST

31. 2026년 3월 6일 PM 2:17 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. We recognize the operational dependency our customers place on this platform and appreciate your partnership during remediation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 10:00 AM PST

32. 2026년 3월 6일 PM 9:10 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. We recognize the operational dependency our customers place on this platform and appreciate your partnership during remediation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: 5:00 PM PST

33. 2026년 3월 7일 AM 1:02 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 7th 12:00 PM PST

34. 2026년 3월 7일 PM 7:55 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 7th 5:00 PM PST

35. 2026년 3월 8일 AM 2:09 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 8th 12:00 PM PST

36. 2026년 3월 8일 PM 7:01 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 8th 5:00 PM PST

37. 2026년 3월 9일 AM 12:37 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 9th 12:00 PM PST

38. 2026년 3월 9일 PM 7:47 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 9th 5:00 PM PST

39. 2026년 3월 10일 AM 1:48 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 10th 12:00 PM PST

40. 2026년 3월 10일 PM 8:15 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 10th 5:00 PM PST

41. 2026년 3월 11일 PM 11:03 UTCmonitoring

    Status: Monitoring Status Update: All services are operating within normal performance thresholds, and validation confirms stable operation. If you experience any issues, please report them to Support so they can be reviewed as part of the ongoing analysis. Next update: March 12th 5:00 PM PST

42. 2026년 3월 13일 PM 7:00 UTCresolved

    Status: Resolved End Time : March 12th 2026 5:00PM PST The issue impacting production workloads in US region has been fully resolved. As of March 5th at 9:05 PM PST, there have been no further disruptions after corrective actions were performed on the Control Plane. All services are operating within normal performance thresholds, and validation confirms stable operation. We recognize the operational dependency our customers place on this platform and appreciate your partnership during remediation.

1. 2026년 2월 25일 PM 10:24 UTCinvestigating

   Production available but materially degraded Status: Investigating Start Time: 2:10PM PST We are investigating performance degradation affecting Log in and API calls in US region. Customers may experience elevated latency or intermittent processing delays. Next update by: 3:30PM PST

2. 2026년 2월 25일 PM 11:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 25일 PM 11:30 UTCinvestigating

   Mitigation Update: Status: Monitoring Last Updated: 3:30 PM PST Remediation steps have been implemented to address performance degradation in US region. We have achieved partial recovery and performance indicators are trending toward baseline levels with no additional services have been impacted. We are maintaining heightened monitoring to confirm sustained stability, and will investigate the root cause upon full recovery. Next update by 4:30 PM PST.

4. 2026년 2월 26일 AM 1:38 UTCmonitoring

   Status: Monitoring Last Updated: 5:30 PM PST The previously implemented remediation steps have addressed the performance degradation in US region and the SnapLogic platform is stable. We have achieved full recovery and performance indicators are at baseline levels. The system was recovered as of 2:55PM PST, however there was a brief performance degradation from 4:02pm PST to 4:13pm PST. We are maintaining heightened monitoring to confirm sustained stability, and are investigating the root cause. Next update by 7.00 PM PST.

5. 2026년 2월 26일 AM 4:42 UTCresolved

   Resolution Status: Resolved End Time: 4:13 PM PST Performance has returned to expected baseline levels. Monitoring confirms stable operation across the affected scope. We will maintain elevated observation as a precautionary measure. Customers requiring operational review may coordinate directly with support.

1. 2026년 2월 24일 AM 8:17 UTCinvestigating

   We have been alerted to issues affecting the SnapLogic platform. Our team is actively investigating the causes of the issue. The following platform services are affected: - UI/Pipeline Development

2. 2026년 2월 24일 AM 10:01 UTCmonitoring

   Performance has been restored to normal. Our monitoring of the US Control Plane of the SnapLogic platform is ongoing. Please open a support ticket with our Support team by emailing [email protected] with any questions or concerns.

3. 2026년 2월 24일 AM 11:30 UTCresolved

   We have fully resolved the issue impacting production workloads in the US region. All services are now operating within normal performance thresholds. We recognize the operational dependency you place on our platform and appreciate your patience during the remediation process. Our teams continue to monitor system health and remain available for direct coordination should you require an additional review.

1. 2026년 2월 23일 PM 5:19 UTCinvestigating

   Status: Investigating Start Time (PST): 9:00 AM PST We are investigating a critical service disruption impacting production workloads in the US region. Customers may experience slowness . At this time, impact is limited to impacted logging into UI. Senior engineering leadership is actively engaged, and remediation efforts are underway. We will provide the next update no later than 10:30AM PST For customers operating mission critical workloads, your designated support channels remain available for direct coordination.

2. 2026년 2월 23일 PM 6:36 UTCinvestigating

   Status: Investigating Start Time (PST): 10:30 AM PST Our team has been working on the critical production disruption that has impacted the SnapLogic platform. At present, the login UI and tasks are now operating as expected and the platform is now stable. We will share a detailed incident summary, including corrective and preventative measures We remain on heightened alert and are monitoring the platform to ensure stability. We will provide the next update no later than 12:00AM PST

3. 2026년 2월 23일 PM 6:36 UTCinvestigating

   We are continuing to investigate this issue.

4. 2026년 2월 23일 PM 8:22 UTCmonitoring

   Status: Monitoring Last Updated: 12:15 PM PST We have worked with all customers who were on the Snaplex 4.44 GA version to transition them to the patched version released on Friday. All systems are stable at this point. We are currently in a state of heightened monitoring to ensure sustained recovery and stability. The next update will be provided by 1:30 PM PST.

5. 2026년 2월 23일 PM 8:22 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026년 2월 23일 PM 10:01 UTCresolved

   Resolution Status: Resolved We have fully resolved the issue impacting production workloads in the US region. All services are now operating within normal performance thresholds. We recognize the operational dependency you place on our platform and appreciate your patience during the remediation process. Our teams continue to monitor system health and remain available for direct coordination should you require an additional review.

1. 2026년 2월 19일 PM 11:46 UTCinvestigating

   Status: Investigating Start Time (PST): 3:02PM PST We are investigating a critical service disruption impacting production workloads in the US region. Customers may experience slowness . At this time, impact is limited to logging into UI, pipeline creation, scheduled tasks, API calls to CP and pipeline initiation. Senior engineering leadership is actively engaged, and remediation efforts are underway. We will provide the next update no later than 4:30PM PST For customers operating mission critical workloads, your designated support channels remain available for direct coordination.

2. 2026년 2월 20일 AM 12:38 UTCinvestigating

   Investigation Update Status: Investigating Last Updated: 4:35 PM PST Performance has been restored to normal, and our investigation into the root cause continues. Containment measures are currently in place, and we have confirmed that no additional regions or platform components have been impacted. We will share further information as it becomes available Next update by: 5:30PM PST

3. 2026년 2월 20일 AM 1:34 UTCinvestigating

   Status: Investigating Last Updated: 5:30 PM PST Performance remains stable, and mitigation measures continue to be effective. Our team is actively investigating the root cause. At this time, there are no new impacts to report, and no additional regions or platform components have been affected. We will provide further updates as more information becomes available. Next update by: 7:30 PM PST

4. 2026년 2월 20일 AM 3:49 UTCmonitoring

   Root Cause Identified & Recovery in Progress Status: Identified Last Updated: 7:45 PM PST We have identified the underlying cause of the disruption affecting production workloads in the Americas region. The issue was caused by a reduction in the HTTP timeout during last night's release, which resulted in service unavailability for the affected scope. Remediation actions are currently in progress, and recovery is being validated against performance baselines. We remain in a state of heightened monitoring to confirm sustained stability. Next update by: 10:00 AM PST, February 20, 2026.

5. 2026년 2월 20일 AM 11:28 UTCinvestigating

   Status: Investigating Start Time (PST): 3:02AM PST We are investigating a critical service disruption impacting production workloads in the US region. Customers may experience slowness . At this time, impact is limited to impacted logging into UI, pipeline creation, Schedule tasks, API calls to CP and pipeline initiation. Senior engineering leadership is actively engaged, and remediation efforts are underway. We will provide the next update no later than 4:30AM PST For customers operating mission critical workloads, your designated support channels remain available for direct coordination.

6. 2026년 2월 20일 PM 12:53 UTCinvestigating

   Status: Investigating Last Updated: 4:45 AM PST System performance remains steady. Our team is actively analyzing the root cause. There are currently no new impacts to report, and no additional regions or platform components have been affected. We will share further updates as soon as more information becomes available. Next update by: 7:30 AM PST

7. 2026년 2월 20일 PM 3:33 UTCinvestigating

   Status: Investigating Start Time (PST): 3:02PM PST, Feb 20th 2026. Our team is still engaged with highest priority on addressing the platform degradation. A corrective action has been taken, after-which the platform has returned to stability. We are closely monitoring the platform, and are working to isolate the root cause as soon as possible. Senior engineering leadership is actively engaged, and remediation efforts are underway. We will provide the next update no later than 10:30 AM PST

8. 2026년 2월 20일 PM 4:26 UTCinvestigating

   Status: Investigating Start Time (PST): 8:01AM PST End Time (PST): 8:11AM PST We are investigating a critical service disruption impacting production workloads in the US region. Customers may experience slowness . At this time, impact is limited to impacted logging into UI, pipeline creation, Schedule tasks, API calls to CP and pipeline initiation. Senior engineering leadership is actively engaged, and remediation efforts are underway. We will provide the next update no later than 10:30AM PST

9. 2026년 2월 20일 PM 6:09 UTCinvestigating

   Status: Investigating We are continuing to investigate a critical service disruption affecting production workloads in the US region. Customers may experience intermittent slowness. Current impact is limited to UI login, pipeline creation, scheduled tasks, API calls to the Control Plane, and pipeline initiation. Senior engineering leadership is actively engaged, and remediation efforts are currently underway. We will provide the next update no later than 11:30 AM PST.

10. 2026년 2월 20일 PM 8:15 UTCinvestigating

    Status: Investigating We are continuing to investigate a critical service disruption affecting production workloads in the US region. Customers may experience intermittent slowness. The same intermittent behavior is occurring with UI login, pipeline creation, scheduled tasks, API calls to the Control Plane, and pipeline initiation. Senior engineering leadership continues to be actively engaged, and remediation efforts are still in progress We will provide the next update no later than 1:30PM PST

11. 2026년 2월 20일 PM 11:03 UTCidentified

    Root Cause Identified: Status: Identified We have identified the underlying cause of the disruption affecting production workloads in the US region. A patch is currently being tested and will be deployed as soon as possible. We will provide the next update no later than 4:30 PM PST.

12. 2026년 2월 21일 AM 1:35 UTCmonitoring

    Status: Monitoring Last Updated: 5:24 PM PST A patch has been deployed to production. We remain in a state of heightened monitoring to confirm sustained recovery. The next update will be provided by 6:00 PM PST.

13. 2026년 2월 21일 PM 5:55 UTCresolved

    Resolution Status: Resolved We have fully resolved the issue impacting production workloads in the US region. All services are now operating within normal performance thresholds, and validation confirms stable operation. We recognize the operational dependency you place on our platform and appreciate your patience during the remediation process. We will share a detailed incident summary, including corrective and preventative measures. Our teams continue to monitor system health and remain available for direct coordination should you require an additional review.

1. 2026년 2월 19일 PM 12:41 UTCinvestigating

   We are currently investigating latency that is occurring on the SnapLogic platform. Our team is investigating the behavior with the highest priority and will update this incident with our progress. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns

2. 2026년 2월 19일 PM 1:44 UTCmonitoring

   Performance has been restored to normal. Our monitoring of the US Control Plane of the SnapLogic platform is ongoing. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

3. 2026년 2월 19일 PM 8:45 UTCresolved

   This incident has been resolved.

1. 2026년 2월 2일 PM 11:56 UTCinvestigating

   We are currently investigating latency that is occurring on the SnapLogic platform. Our team is investigating the behavior with the highest priority and will update this incident with our progress. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

2. 2026년 2월 3일 AM 12:01 UTCmonitoring

   Performance has been restored to normal and latency should no longer be occurring. Our monitoring of the US Control Plane of the SnapLogic platform is ongoing. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

3. 2026년 2월 3일 AM 1:39 UTCresolved

   The latency that had been occurring on the US Control plane of the SnapLogic platform has been addressed after corrective actions were taken. As the expected levels of performance and stability have been returned to the US Control Plane, this issue is now resolved. Please contact Support team by emailing [email protected] with any questions or concerns.

1. 2025년 11월 18일 PM 12:07 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 11월 18일 PM 12:13 UTCinvestigating

   We are currently working with the Cloudflare vendor regarding an issue that seems to be impacting only the login. We are actively investigating this and will provide an update as soon as possible. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

3. 2025년 11월 18일 PM 12:43 UTCinvestigating

   We are continuing to investigate this issue.

4. 2025년 11월 18일 PM 2:40 UTCmonitoring

   Cloudflare has restored service and we are seeing UI Login is working as expected. Continuing to monitor.

5. 2025년 11월 18일 PM 8:01 UTCresolved

   This incident has been resolved.

1. 2025년 9월 24일 PM 9:53 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 9월 24일 PM 10:49 UTCmonitoring

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

3. 2025년 9월 25일 PM 2:03 UTCresolved

   This incident has been resolved.

1. 2025년 8월 18일 PM 5:19 UTCinvestigating

   We’ve been made aware of slowness in the SnapLogic Platform, that is impacting pipeline preparation from ground nodes. Our team is actively investigating. Iif you notice any unusual behavior, please reach out to support through the usual channels ([email protected]).

2. 2025년 8월 18일 PM 6:39 UTCmonitoring

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

3. 2025년 8월 18일 PM 8:28 UTCresolved

   This incident has been resolved.

1. 2025년 7월 16일 PM 7:46 UTCinvestigating

   We are currently investigating latency that is occurring on the SnapLogic platform, and is impacting the performance of Task executions. Our team is investigating the behavior with the highest priority and will update this incident with our progress. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

2. 2025년 7월 16일 PM 9:07 UTCinvestigating

   Latency is still observed on the SnapLogic platform and our team is still working on identifying the root cause of the issue with the highest priority. We apologize for any inconvenience. Please open a support ticket with our Support team by emailing [email protected] with any questions or concerns.

3. 2025년 7월 16일 PM 9:31 UTCmonitoring

   We have identified the cause of the problem, and have taken corrective action to prevent further latency on the SnapLogic platform. We are monitoring the platform to ensure continued stability. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

4. 2025년 7월 17일 PM 3:05 UTCinvestigating

   We are investigating additional latency on the SnapLogic platform and are working on additional corrective actions. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

5. 2025년 7월 17일 PM 3:36 UTCmonitoring

   Corrective action has been taken to address the latency on the SnapLogic platform. We are monitoring the platform to ensure stability. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

6. 2025년 7월 17일 PM 4:38 UTCmonitoring

   Performance has been restored to normal and latency should no longer be occurring. Our monitoring of the US Control Plane of the SnapLogic platform is ongoing. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

7. 2025년 7월 17일 PM 5:35 UTCresolved

   The latency that had been occurring on the US Control plane of the SnapLogic platform has been addressed after corrective actions were taken. As the expected levels of performance and stability have been returned to the US Control Plane, this issue is now resolved. Please open a support ticket with out Support team by emailing [email protected] with any questions or concerns.

1. 2025년 6월 2일 PM 6:10 UTCinvestigating

   We have observed on the Snaplogic EMEA control plane that when logging in, users will receive the error "Error occurred while initializing Pipeline schema" Try again later Internal Server Error. Snaplogic is working on resolving the issue as soon as possible with the highest priority . Please contact our Support team at [email protected] with any concerns.

2. 2025년 6월 2일 PM 6:35 UTCmonitoring

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

3. 2025년 6월 2일 PM 6:35 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 6월 2일 PM 9:25 UTCresolved

   This incident has been resolved.

1. 2024년 10월 10일 AM 7:59 UTCidentified

   We’ve been informed of issues with SSO logins to the UI following the October patch release. To avoid disrupting our customers using SSO, we’ve decided to roll back the October release. If you encounter any unusual behavior in the meantime, please reach out to support.

2. 2024년 10월 10일 AM 8:16 UTCmonitoring

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

3. 2024년 10월 10일 AM 9:16 UTCresolved

   This incident has been resolved.

1. 2024년 2월 23일 AM 5:14 UTCinvestigating

   We have been alerted to failures for logins to the UI. Our team is currently investigating. In the meantime, if you experience any unusual behavior, please contact support ([email protected])

2. 2024년 2월 23일 AM 6:36 UTCmonitoring

   There was an issue with multiple sldb servers going down causing platform latency which caused login failures to the platform as well as API requests timed out. The servers started back up and Snaplogic is investigating the root cause. Will provide an RCA soon.

3. 2024년 2월 23일 PM 7:27 UTCresolved

   This incident has been resolved.

1. 2023년 9월 28일 AM 10:53 UTCinvestigating

   We have been alerted to slowness in the SnapLogic Platform UI. Our team is currently investigating. In the meantime, if you experience any unusual behavior, please contact support in the usual way ([email protected])

2. 2023년 9월 28일 AM 11:21 UTCmonitoring

   There was a spike in the platform latency which was caused by an unexpected and abnormally high volume of requests. A fix has been implemented and we are monitoring the results.

3. 2023년 9월 28일 PM 5:04 UTCresolved

   This incident has been resolved.

1. 2023년 6월 22일 PM 4:50 UTCinvestigating

   We have been alerted to an elevated level of errors from the SnapLogic Platform. Our team is currently investigating this issue. In the meantime, if you experience any unusual behavior, please contact support in the usual way ([email protected])

2. 2023년 6월 22일 PM 5:39 UTCinvestigating

   The SnapLogic platform has encountered a problem due to a database level issue. This has caused UI slowness and failures in pipeline initiations that are dependent on the control plane. The team is actively working on the issue with all hands on deck, and will provide additional updates ASAP.

3. 2023년 6월 22일 PM 5:40 UTCinvestigating

   We are continuing to investigate this issue.

4. 2023년 6월 22일 PM 6:34 UTCmonitoring

   A db issue has been identified and a fix has been applied and are monitoring.

5. 2023년 6월 22일 PM 11:14 UTCresolved

   This incident has been resolved.

1. 2023년 6월 15일 AM 3:36 UTCinvestigating

   We have been alerted to failures for SSO logins to the UI. Our team is currently investigating. In the meantime, if you experience any unusual behavior, please contact support ([email protected])

2. 2023년 6월 15일 AM 5:28 UTCmonitoring

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

3. 2023년 6월 15일 PM 5:21 UTCresolved

   This incident has been resolved.