The impact varied by cell and features in use.\r\n\r\nImpact across US Cells 1, 2, 3 and 4:\r\n-Users were unable to authenticate into orgs with Custom Domains until 4:00PM PDT\r\n-AD and LDAP agents could not connect to Okta until 4:17PM PDT. \r\n \r\nRoot Cause Summary:\r\nPrior to the AWS Account Federation app upgrade, a code change had been made to how provisioning options were handled when migrating customers to a new app version. Okta isn't able to probe for device context, so users are denied access when they authenticate with a username and password. At 12:52 pm (PST) a customer reported lack of access to the LDAP Interface and Okta began investigating. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000007eJOWUA2"},"Id":"a1P0Z000007eJOWUA2","CreatedDate":"2018-04-23T17:44:08.000+0000","IncidentId__c":"a9C0Z000000TNelUAG","UpdateLog__c":"Okta continues to investigate an issue with the /api/v1/events endpoint in all cells. The database cluster was not configured to support this number of connections, causing the database cluster to become unresponsive.\r\n\r\nAt approximately 3:10PM (PT) Okta engineers reverted the migration, directing all traffic to the original ASGs, and began downsizing the new ASGs to reduce the number of open connections. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSKfEAM"},"Id":"a1P4z000009mSKfEAM","CreatedDate":"2023-03-04T02:12:49.000+0000","IncidentId__c":"a9C4z000000YznUEAS","UpdateLog__c":"Okta has completed all automated remediation actions. The issue could prevent Helpdesk Admins from being able to reset a users password via a temporary password. We will provide an update in 30 minutes or sooner if additional information becomes available. We anticipate that this restoration will happen over the next hour.\r\n\r\nCustomers who have previously noticed this should review their flow execution history to ensure correct processing. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000Fj045UAB"},"Id":"a1P2A00000Fj045UAB","CreatedDate":"2017-05-15T14:19:12.000+0000","IncidentId__c":"a9C2A000000blruUAA","UpdateLog__c":"Interactive user experience has returned to normal in US Cell 2. You can also sign in to apps with Okta Verify push notifications if your organization configured this option. We are actively investigating and will update this message with more information as soon as we have it. \r\n\r\nA small subset of pre-production customers that utilize customized sign-in pages in the US Preview environment with a custom authorization server on Okta Classic experienced repeated page load errors. We will provide an update in 30 minutes or sooner if additional information becomes available. At approximately 2:13 PM PDT the fix was fully deployed and generated emails were sent with visible temporary passwords. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKsqEAH"},"Id":"a1P4z00000BAKsqEAH","CreatedDate":"2022-02-04T20:24:47.000+0000","IncidentId__c":"a9C4z000000wkADEAY","UpdateLog__c":"We sincerely apologize for any impact this incident has caused you, your business or your customers. An RCA will be provided following full investigation. At 9:07PM application servers were set to the correct active state with full access to the primary and read-only database tiers. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mS9XEAU"},"Id":"a1P4z000009mS9XEAU","CreatedDate":"2023-02-02T15:06:24.000+0000","IncidentId__c":"a9C4z000000YzlEEAS","UpdateLog__c":"At 6:08 AM PST on February 2, 2023, Okta became aware of network connectivity issues affecting customers in US Cell-7. Manage settings Configure Windows Hello, manage the display theme, or join beta to test new app versions. After you close Okta Verify, the code is no longer generated. We are continuing to monitor. Please expect the next update at or before 7:30PM PDT. \r\n\r\nSome customers will still have inconsistent data and we are investigating options to recover this data.\r\n\r\nWell provide an update in an hour, or sooner if additional information becomes available. At this time user provisioning has been disabled, we are working to restore this functionality and investigating the root cause. Using the first enrolled device, open a browser, and then go to your End-User Dashboard. Were reverting the update to remediate the problem","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005XZDOUA4"},"Id":"a1P0Z000005XZDOUA4","CreatedDate":"2018-09-05T19:16:27.000+0000","IncidentId__c":"a9C0Z0000008PU1UAM","UpdateLog__c":"We are actively working with Microsoft who has reported this is related to mitigation activities from yesterday's service disruption (MO147606):\r\n\r\n\r\n\"We identified and reverted an update that was causing multiple services to be throttled. Biometrics isn't supported on Android 12 if, Push notification: Number challenge isn't supported in LDAPi and RADIUS environments. Ensure that your network connection is stable. Additional root cause information will be provided within 48 hours. Please contact support if you are having difficulty setting up provisioning and we will assist with implementation of an applicable workaround as we investigate further. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRdgEAE"},"Id":"a1P4z000009mRdgEAE","CreatedDate":"2022-11-05T23:39:55.000+0000","IncidentId__c":"a9C4z000000YzhlEAC","UpdateLog__c":"Okta continues to monitor the current situation with Okta email delivery for Yahoo email end users. During the creation of the new virtual firewall rule the permissive ingress part of the rule was mistakenly omitted, thereby inhibiting requests from reaching the next layer in the infrastructure in US Cell 10. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000009QRj7UAG"},"Id":"a1P1Y000009QRj7UAG","CreatedDate":"2021-02-05T19:10:28.000+0000","IncidentId__c":"a9C1Y0000008PgWUAU","UpdateLog__c":"Root Cause Analysis:\r\n\r\nAt approximately 12:20 pm (PST) on Tuesday February 2nd, a required infrastructure maintenance event caused a partial loss of network connectivity to the LDAP Interface for Okta customers within US Cell 5.\r\n\r\n\r\nDue to mis-prioritization of the monitoring alerts that fired, Okta did not get automatically notified of the impact. End users in US Cell 2 attempting to reach Okta received HTTP 500 errors, and customer integrations attempting to reach Okta API endpoints in US Cell 2 encountered elevated response times and errors. At approximately 11:28 AM PDT, all errors had been cleared. User authentication was not impacted at any point.\r\nThe root cause was traced to a serialization bug that affected a portion of Office365 application tenants. The Advanced Server Access team is investigating and taking action to restore the services.\r\n\r\nWell provide an update in 30 minutes, or sooner if additional information becomes available. We will provide an update within the next 30 minutes. \r\n\r\nWe will provide an update 30 minutes or sooner. System responsiveness and major functionality have returned to normal. We see improvement in delivery rates.\r\nOur next update will be at 9:00 am PT on 11/7 or sooner if additional information becomes available. At approximately 11:35 AM, service was fully restored for all customers in all cells.\r\n\r\nAdditional testing and alerting to prevent and detect such issues will be implemented to prevent future occurrences. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRVDEA2"},"Id":"a1P4z000009mRVDEA2","CreatedDate":"2022-10-17T16:05:03.000+0000","IncidentId__c":"a9C4z000000Yzh7EAC","UpdateLog__c":"An issue impacting Okta Verify Application version 7.9.1 functionality for Android devices in all cells is being investigated. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000G0UouUAF"},"Id":"a1P2A00000G0UouUAF","CreatedDate":"2018-03-07T19:35:41.000+0000","IncidentId__c":"a9C2A000000PBikUAG","UpdateLog__c":"The issue impacting API Access Management in US Preview cell has been resolved for the majority of customers. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zHjoUAE"},"Id":"a1P1Y000007zHjoUAE","CreatedDate":"2019-09-30T23:20:43.000+0000","IncidentId__c":"a9C1Y0000004DyLUAU","UpdateLog__c":"Weve narrowed the issue down to Google Chrome version 77 (on both desktop and Android). Error rates are improving and we remain actively engaged on the issue. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mS5QEAU"},"Id":"a1P4z000009mS5QEAU","CreatedDate":"2023-01-23T18:09:03.000+0000","IncidentId__c":"a9C4z000000YzkkEAC","UpdateLog__c":"Okta has identified the root cause of IdP-initiated login to specific Microsoft O365 apps (impacted apps: Word, Excel, PowerPoint) issue affecting customers in all cells. The fix was fully deployed to all impacted cells by 6:17 PM PST.\r\n\r\nOkta worked with, and mitigated the issue for, customers that requested an expedited resolution ahead of the rollout of the fix.\r\n\r\nPreventive Actions:\r\n\r\nOkta has added additional testing, monitoring, and alerting for the Group Push feature in the O365 application to prevent future occurrences. You can find the knowledge article at support.okta.com. Clearing browser cookies will help mitigate the Multifactor Authentication redirect loop. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSKkEAM"},"Id":"a1P4z000009mSKkEAM","CreatedDate":"2023-03-04T03:39:35.000+0000","IncidentId__c":"a9C4z000000YznUEAS","UpdateLog__c":"Okta is developing a KB article and additional information to assist customers that were impacted by this issue. Root Cause Analysis will be provided here within 2 business days. We are actively working with our providers to resolve the issue and will provide an update when we have further information. If you need immediate assistance in resolving the issue, please contact Okta Customer Support. The next update will take place at 11:45am PT or as soon as additional details become available. During a scheduled certificate update, a non-customer facing certificate for an internal load balancer was updated across all production cells. As the service failed, it automatically restarted repeatedly which resulted in the intermittent success spikes during this period.\r\n\r\nAt approximately 10:18 pm (PST) Okta added additional infrastructure to the impacted tier to mitigate impact while addressing the root cause. If the Okta Verify app isn't running in the background, Okta isn't able to probe for device context and the user may be denied access depending on the app sign-on policy. Okta Verify for Android, as well as Okta Verify for iOS 13 and iOS 14, are working as expected. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKn2EAH"},"Id":"a1P4z00000BAKn2EAH","CreatedDate":"2021-11-09T00:15:07.000+0000","IncidentId__c":"a9C4z000000wk5cEAA","UpdateLog__c":"Okta is seeing sustained successes in Workflow Console, flow invocation, and all services are running without any issues. ","Status__c":"Resolved","Start_Date__c":"2021-11-08","End_Date__c":"2021-11-08","Last_Updated__c":"2021-11-10T17:12:55.000+0000","LastModifiedDate":"2022-03-04T18:11:39.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Size__c":"Small","Incident_Title__c":"Errors Invoking New Workflows, Utilizing Workflows Designer, and Hook Delays","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2021-11-08T20:46:00.000+0000","CreatedDate":"2021-11-08T20:48:43.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000wk8HEAQ"},"Id":"a9C4z000000wk8HEAQ","Duration__c":1800,"Log__c":"Okta has identified the issue with the NetSuite Import and successfully deployed a fix to resolve it. They can work around this issue by entering the verification code displayed on Okta Verify. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000AqaaoEAB"},"Id":"a1P4z00000AqaaoEAB","CreatedDate":"2022-11-16T23:33:41.000+0000","IncidentId__c":"a9C4z000000Yzi5EAC","UpdateLog__c":"Okta has provided a self-service guide to help resolve the authentication issues for Office 365 applications. Okta Provisioning and SSO services were affected as a result of this outage across all cells.\r\n\r\nOn March 16th, at 2:25am PDT, Microsoft declared the incident resolved. When enabled, Risk Scoring assigns a risk level to each Okta sign-in, and admins can configure a sign-on policy rule to take different actions based on the risk level of the sign-in, such as prompting for multifactor authentication if the sign-in is considered high-risk. Further updates can be found in the admin portal under EX147785 and MO147789.\"","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005XZU5UAO"},"Id":"a1P0Z000005XZU5UAO","CreatedDate":"2018-09-18T01:23:42.000+0000","IncidentId__c":"a9C0Z0000008PUVUA2","UpdateLog__c":"End users are currently experiencing errors when authenticating to O365. Our next update will be in an hour or sooner if additional information becomes available. Logs are included automatically. During this period, the success rate was about 40% for customers accessing US Cell 5 due to the applications fluctuating between an available and unavailable state. Sign in with Okta FastPass isn't supported in WebView on native Android apps. We request that customers needing assistance implementing the resolution contact Okta Support. At Okta trust and transparency are our top priorities. During the event, user updates to the Zoom application may have encountered errors if the provisioned user already existed within Zoom. The LDAP Interface service was fully restored to all customers on US Cell 5 by 4:50pm (PST).\r\n\r\n\r\nImmediately after resolution, Okta implemented updates to internal monitoring and alerting in order to close the identified monitoring gap. We are committed to implementing improvements to the service to prevent future occurrences of this incident.\r\n\r\n \r\nDetection and Impact\r\n\r\nOn March 3, 2023 at 3:20 am (PST), Okta monitoring began receiving customer reports of failed execution requests using Workflows Tables on EU Cells 1 and 2. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000009QRDfUAO"},"Id":"a1P1Y000009QRDfUAO","CreatedDate":"2020-11-26T11:41:10.000+0000","IncidentId__c":"a9C1Y0000008PepUAE","UpdateLog__c":"The processing delays have been resolved for OK1, OK2, OK3, and OK4, and System Logs are up-to-date. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zHpmUAE"},"Id":"a1P1Y000007zHpmUAE","CreatedDate":"2019-10-04T02:10:12.000+0000","IncidentId__c":"a9C1Y0000004DyLUAU","UpdateLog__c":"Root Cause Analysis: On Sept 30th, at approximately 3:39PM PDT, customers reported experiencing longer than expected load times for application logos in the Okta end-user dashboard and catalog.\r\n\r\nUpon investigation, Okta determined users in all cells experienced the longer load times after updating their Chrome browser to version 77.0.3865.75 (Official Build) (64-bit). Okta Verify features are available based on configurations made by your organization. By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. Our next update will be in an hour or sooner if additional information becomes available. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000Fj04ZUAR"},"Id":"a1P2A00000Fj04ZUAR","CreatedDate":"2017-05-15T15:03:33.000+0000","IncidentId__c":"a9C2A000000blruUAA","UpdateLog__c":"RESOLVED: 8:02am PDT: An issue impacting system responsiveness, including interactive performance and job processing in US Cell 2 was addressed. On September 29 at approximately 2:40 am PDT, service was fully restored. The remaining queued jobs are processing at full capacity and we will continue to monitor. Additional root cause information will be provided in 2 Business days. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSKpEAM"},"Id":"a1P4z000009mSKpEAM","CreatedDate":"2023-03-04T04:21:17.000+0000","IncidentId__c":"a9C4z000000YznUEAS","UpdateLog__c":"Okta has completed restoration for the majority of customers affected. Additional root cause information will be provided in 48 hours. While being reported as NOT_CONNECTED, monitoring shows that AD Agent authentication continues to be successful. Credentials are earned by passing an Okta certification exam, series of exams, or by fulfilling other performance-based activities. Why this promisified JWT.verify isn't working? However, residual impacts to provisioning were observed for some customers as Microsoft propagates changes across Microsofts services.\r\n\r\nWhile the majority of Oktas customers have fully recovered, as part of Oktas on-going commitment to our customers, we are assisting our customers in working w/ Microsoft to address any residual issues as a result of the Microsoft outage. Okta continued monitoring and confirmed at 1:18PM, that the service was restored and operating as expected. The service was fully restored at 6:27AM PST. \r\n\r\n \r\n\r\nOktas monitoring has determined that there are three categories of impact: \r\n\r\n \r\n\r\nCategory 1: Inbound connections to Okta and errors from the Okta service starting at 9:56AM\r\n\r\nUS Cell 6: up to 34% failure rate, ending at 10:36AM \r\n\r\nUS Cell 10: up to 7% failure rate, ending at 10:39AM \r\n\r\nUS Cell 11: up to 24% failure rate, ending at 10:39AM \r\n\r\n \r\n\r\nCategory 2 (US Cell 6 and US Cell 10): Cells were in Read Only Mode starting at 9:56AM\r\n\r\nUS Cell 6: ending at 11:27AM\r\n\r\nUS Cell 10: ending at 11:37AM\r\n\r\nCategory 2 (US Cell 11): Increased error rates due to internal networking infrastructure errors starting at 9:56AM\r\n\r\nUS Cell 11: up to 12% failure rate, ending at 11:05AM\r\n\r\n \r\n\r\nCategory 3 : Job processing impacts starting at 9:56AM\r\n\r\nUS Cell 6: ending at 12:12PM \r\n\r\nUS Cell 10: ending at 12:08PM \r\n\r\nUS Cell 11: ending at 12:13PM \r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nOktas cloud service provider experienced a loss of power incident which resulted in a partial outage in a single availability zone within a region causing inbound and outbound connection errors that impacted the Okta service. However, due the complexity of the process of enabling the API Access Management feature, it took Okta longer than usual to restore the feature to entitled tenants. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000B1wSOEAZ"},"Id":"a1P4z00000B1wSOEAZ","CreatedDate":"2021-03-07T18:30:27.000+0000","IncidentId__c":"a9C4z000000oLkPEAU","UpdateLog__c":"We continue to investigate the intermittent issues with external network connectivity in the OK8 (APAC) region. Okta engaged with its downstream vendors to address the issue, and as the issue progressed, Okta was notified of, and implemented, a workaround by switching the short code SMS sender ID to a toll free number.\r\n\r\nPreventive Actions:\r\nThe root cause of the issue occurred within the telecommunication infrastructure rather than with one of Okta's downstream telecommunications providers. We will provide an update in 30 minutes or sooner if additional information becomes available. Okta Engineering is actively working on a fix and will release new versions of Okta Mobile and Okta Verify as soon as they are ready. At approximately 2:30pm PDT, Okta started to see improvements in Single Sign-On (SSO) and the Provisioning services. Due to this regression, Help desk Admins were unable to trigger a user password reset through the Okta Admin UI. Engineering is working to identify the list of customers still impacted and is investing a way to proactively address the issue for these customers. Remaining impacted customers have been notified via in product notification on additional actions to resolve the situation. ","Status__c":"Resolved","Start_Date__c":"2021-08-25","Last_Updated__c":"2021-08-28T07:06:52.000+0000","LastModifiedDate":"2021-08-28T07:06:52.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Size__c":"Large","Impacted_Cells__c":"okta.com:12","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2021-08-26T03:09:00.000+0000","CreatedDate":"2021-08-26T03:09:49.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000wk2nEAA"},"Id":"a9C4z000000wk2nEAA","Duration__c":115,"Log__c":"Beginning at approximately 5:27AM PDT, customers leveraging SMS as a factor may have experienced intermittent delivery delays to U.S based numbers upon first attempt. I set up Okta Verify, but at the end, the green checkmark didnt appear, and I got an error on my device. I can't sign in to my account even if I approve the push notification sent to my device. While the message displayed in the app may sound alarming, the issue is benign, and due to our over abundance of caution with TLS algorithm restrictions. \r\n\r\nRoot Cause Summary:\r\nOkta identified a significant increase in request traffic against OK10 which exhausted some edge service resources, resulting in slow and failed requests.\r\n\r\nRemediation Steps:\r\nUpon investigation, Okta identified the source of the increased traffic, and at 10:13 AM (PDT) throttled the excess request traffic. ","Status__c":"Resolved","Start_Date__c":"2023-02-02","End_Date__c":"2023-02-02","Last_Updated__c":"2023-02-07T08:48:45.000+0000","LastModifiedDate":"2023-02-07T08:48:45.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Size__c":"Small","Incident_Title__c":"US Cell-7 network connectivity issues","Impacted_Cells__c":"okta.com:7","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2023-02-02T14:42:00.000+0000","CreatedDate":"2023-02-02T14:43:53.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000YzkkEAC"},"Id":"a9C4z000000YzkkEAC","Duration__c":8204,"Log__c":"Okta became aware of IdP-initiated login (login via Okta Dashboard) in Microsoft O365 app issue affecting customers in all cells. No production cells were impacted.\r\n\r\n\r\nRoot Cause Summary: \r\n\r\nAn update for the Content Security Policy (CSP) header enforcement for non-customizable pages caused a regression in a specific use case in the Preview sandbox environment. Further investigation revealed that the success rate of requests was highly intermittent during this period and also dependent on the location of the Okta user. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zKcbUAE"},"Id":"a1P1Y000007zKcbUAE","CreatedDate":"2020-02-28T02:54:36.000+0000","IncidentId__c":"a9C1Y0000004EBtUAM","UpdateLog__c":"Okta is continuing to work towards a fix that will resolve this issue. Device lifecycle messages aren't available on macOS devices that use an SSO extension profile. As part of our on-going focus on reliability, Okta is also working to implement more granular monitoring and automated mitigation mechanisms to protect against similar issues during future infrastructure updates. The degree of impact varied depending on each customers implementation and client-side caching. \r\n\r\n\r\nRemediation Steps: \r\n\r\nDuring the incident, Okta deployed additional traffic management rules to mitigate the impact including moving some traffic to isolated infrastructure. \r\n\r\nPreventative Actions:\r\n\r\nOkta is reviewing and investigating how to improve the correlation of increased error rates to a geographic origin when the aggregate error rate is relatively small. Learn how to troubleshoot Okta Verify problems. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005XZDTUA4"},"Id":"a1P0Z000005XZDTUA4","CreatedDate":"2018-09-05T19:31:37.000+0000","IncidentId__c":"a9C0Z0000008PU1UAM","UpdateLog__c":"Resolved: An issue impacting authentication and system responsiveness for a subset of end-users and administrators accessing Microsoft Office 365 has subsided. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRZUEA2"},"Id":"a1P4z000009mRZUEA2","CreatedDate":"2022-10-27T00:18:14.000+0000","IncidentId__c":"a9C4z000000YzhMEAS","UpdateLog__c":"We sincerely apologize for any impact this incident has caused you and your business, and your customers. Okta has reconfigured it's load balancers across all cells to avoid a recurrence of the issue. See About Risk Scoring. Our next update will be in 12 hours or sooner if additional information becomes available","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000007sujAEAQ"},"Id":"a1P4z000007sujAEAQ","CreatedDate":"2022-07-28T19:45:35.000+0000","IncidentId__c":"a9C4z0000012OTZEA2","UpdateLog__c":"An issue impacting network connectivity in US Cell-6, US Cell-10 and US Cell-11 was addressed. This fix was deployed to US Cell 1 at 8:49pm PST and then to all cells. \r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, Okta is including additional runbook improvements and adding additional capacity to the affected infrastructure component. Additional information is in https://status.okta.com/#incident/a9C4z000000wkAXEAY","Status__c":"Resolved","Start_Date__c":"2022-02-03","End_Date__c":"2022-02-03","Last_Updated__c":"2022-02-08T14:35:42.000+0000","LastModifiedDate":"2022-02-08T14:35:42.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Size__c":"Small","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:5;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:10;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta-gov.com:1;okta.com:16","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"MFA","Start_Time__c":"2022-02-03T17:32:00.000+0000","CreatedDate":"2022-02-03T17:33:46.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000wkADEAY"},"Id":"a9C4z000000wkADEAY","Duration__c":1501,"Log__c":"Resolved: An issue impacting Authentication for certain embedded browser usecases for all endusers in US-Cell 1 and US-Cell 9 was addressed.
Project Management Concentration, Completed Works Scrunch Earrings, Yotel Glasgow Contact Number, Does State Farm Raise Rates After Comprehensive Claim, Curlmix Flaxseed Gel Ingredients, Fiskars Cutting Mat 18x24, Goldfinger Potentilla Drought Tolerant, Where To Buy Caputo Flour Near Me, Dewalt Plastering Tools,
