Is Okta FGA Down Right Now? Check if there is a current outage ongoing.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20250312-Elevated_Errors_in_FGA_US-1_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20250312-Elevated_Errors_in_FGA_US-1_Public_Cloud_Environment.pdf)

Our Engineering team implemented a fix and issue has been resolved. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

On March 12, 2025, between 20:11 and 20:14 UTC, we experienced elevated errors in our FGA US-1. Users who were affected would have experienced 5xx error codes when attempting to perform Check API authorization requests. There is no active impact, and no actions are required from our customers.

We have thoroughly investigated the service interruption encountered in this event and determined that a broad disruption was not applicable. Following a period of stability, we have downgraded the severity of the incident, and our support teams will continue to assist any impacted customers by improving the errors they may have experienced.

Services has been restored. We sincerely apologize for the impact this had on you and your users.

The system self-recovered and we are monitoring the system.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250108\_Increased\_Error\_Rates\_for\_FGA\_Public\_Cloud\_Environment.pdf](https://cdn.auth0.com/blog/20250108_Increased_Error_Rates_for_FGA_Public_Cloud_Environment.pdf)

This issue has been fully resolved. An root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for any impact this has caused you and your users.

Our Engineering team identified an issue earlier which had also caused some minor impact to services on the FGA Dashboard. Impacted customers may have observed an error when creating a store. This was fully resolved with our mitigation efforts earlier and there is no residual impact to the FGA Dashboard.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250108\_Increased\_Error\_Rates\_for\_FGA\_Public\_Cloud\_Environment.pdf](https://cdn.auth0.com/blog/20250108_Increased_Error_Rates_for_FGA_Public_Cloud_Environment.pdf)

This issue has now been fully resolved and mitigated. In some rare customer exception cases, customers may need to generate a new token for their client. Otherwise, customers should automatically receive a new token and no longer encounter any issues. Should you have any further questions, please contact our Support team. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for any impact this has caused you and your users.

We are observing full recovery now and our Engineering team is continuing to monitor this issue.

We are working to gradually mitigate this for all impacted FGA customers and we expect all mitigation and testing to complete within one hour. Customers should start to gradually see improvements for their implementations within the hour. We will post here once all mitigation efforts are completed and error rates have fully subsided on all customer environments.

Our Engineering team has identified the root cause for this issue. We are working immediately to mitigate the misconfiguration which appears to be causing these errors and we will advise here once these errors have subsided. We will post additional updates to this page in approximately 30 minutes once this work has been fully completed.

Our Engineering team is continuing to investigate this issue and we will share additional information as our investigation progresses. We will post an additional update here in 15 minutes.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20241219-Elevated_Error_Rates_in_the_FGA_US-1_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20241219-Elevated_Error_Rates_in_the_FGA_US-1_Public_Cloud_Environment.pdf)

Services have been stable. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

We have identified the root cause of the issue and have deployed a fix. The errors have subsided and we will continue to monitor the situation.

Our Engineering team is currently triaging the issue and determining applicable mitigation actions. The affected users may continue to experience 5xx error codes when attempting to perform authorization requests. We will post more updates here in 15 minutes.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20241111_Increased_Error_Rates_on_FGA_US1.pdf](https://cdn.auth0.com/website/20241111_Increased_Error_Rates_on_FGA_US1.pdf)

Services are restored and the environment is functioning as expected. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

Our Engineering team has identified a series of error rate spikes which impacted core services in FGA US-1 from approximately 18.30 to 18.33 UTC. There is no current impact to the environment and our Engineering team is continuing to review this issue.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20241031\_Increased\_Error\_Rates\_on\_FGA\_US1.pdf](https://cdn.auth0.com/website/20241031_Increased_Error_Rates_on_FGA_US1.pdf)

Services are working as expected. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

Following our review of the issue that occurred on October 31, 2024 for FGA US-1, our Engineering team has identified a brief second error rate spike that occurred from approximately 15:59 to 16:04 UTC on October 31. There is no current impact to FGA services and this issue has since been resolved.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20241031_Increased_Error_Rates_on_FGA_US1.pdf](https://cdn.auth0.com/website/20241031_Increased_Error_Rates_on_FGA_US1.pdf)

Services in the environment are functioning as expected and this issue has been resolved. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

Our Engineering team is observing recovery now and services are functioning in the environment as expected.

Additional mitigation actions are underway to resolve this issue. We will post additional updates here in approximately 20 minutes.

Our Engineering team is continuing to review all relevant mitigation actions for this issue as we work to resolve this urgently. We will provide additional updates here in 15 minutes.

Our Engineering team has identified the root cause of this issue and we are reviewing any applicable mitigation actions. We will provide additional updates here in 15 minutes.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20241024-Elevated_Error_Rates_in_the_FGA_US1_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20241024-Elevated_Error_Rates_in_the_FGA_US1_Public_Cloud_Environment.pdf)

The errors self-resolved and the services have been stable. We will continue to investigate the issue’s root cause and provide an analysis within 14 days. We sincerely apologize for the impact this had on you and your users.

On October 24, 2024, between 04:12 AM and 04:23 AM UTC, we experienced elevated errors in our FGA US-1. Users who were affected would have experienced 5xx error codes when attempting to perform authorization requests. There is no active impact, and no actions are required from our customers.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2024_09_17_Increased_Errors_in_FGA_US1.pdf](https://cdn.auth0.com/website/2024_09_17_Increased_Errors_in_FGA_US1.pdf)

Services has been restored.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20240823_Increased_Error_Rates_on_FGA_US1.pdf](https://cdn.auth0.com/website/20240823_Increased_Error_Rates_on_FGA_US1.pdf)

Services have been restored. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

Our Engineering team has observed increased error rates that impacted FGA core services briefly from approximately 17:31 to 17:41 UTC. This issue has now resolved and our team is continuing to review.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20240801 - Elevated Error Rates in FGA-1 Public Cloud Environment.pdf](https://cdn.auth0.com/website/20240801 - Elevated Error Rates in FGA-1 Public Cloud Environment.pdf)

Services has been stable. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

We applied a fix for the issue and are monitoring the system.

Customers impacted by this event would have received 500 error codes when attempting to perform authorization requests. We have identified the root cause of the issue and are implementing a fix. We will provide updates as soon as they’re available.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20240702_Increased_Error_Rates_in_FGA_EU1.pdf](https://cdn.auth0.com/website/20240702_Increased_Error_Rates_in_FGA_EU1.pdf)

Services have been stable. A root cause analysis (RCA) will be posted here within 14 days.

Our monitoring detected a sudden increase in load balancer errors in the FGA EU-West-1 Public Cloud Environment from approximately 14:15 to 14:42 UTC. The issue has self-resolved, and our customers are not required to take any action.

We are currently investigating an incident. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20240417_FGA_Authentication_Failures.pdf](https://cdn.auth0.com/website/20240417_FGA_Authentication_Failures.pdf)

Services has been restored. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

We applied a fix for the issue and are monitoring the system.

We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information

This incident has been resolved.

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

We have identified the issue and are currently working on restoring the service.