Okta FGA Outage History

Started Sep 22, 2026, 01:20 AM UTC· resolved Oct 07, 2026, 12:30 PM UTC

1. identified Sep 22, 2026, 01:20 AM UTC

   We are seeing a delay in log ingestion on US1. If you are using Auth0 FGA Logging (https://docs.fga.dev/fga-logging), the logs are still available, though will take a while to show up in the API or Dashboard. We're looking into it.

2. resolved Oct 07, 2026, 02:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 08:15 PM UTC· resolved Sep 16, 2026, 08:59 PM UTC

1. investigating Sep 16, 2026, 08:33 PM UTC

   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.

2. identified Sep 16, 2026, 08:41 PM UTC

   We're investigating an issue impacting the FGA EU-1 Environment. We're in the process of formulating our mitigation action in the form of a rollback. We'll provide updates the status of this event changes.

3. monitoring Sep 16, 2026, 08:55 PM UTC

   Our rollback procedure has completed on a deployment that was recently applied to the affected environment. In tandem with the rollback, we've scaled up backend resources to mitigate customer impact. Our monitoring systems indicate that service error rates are subsiding at this time. We're continuing to investigate the specific behavior behind the root cause of the event. We'll provide further updates regarding changes in incident status.

4. resolved Sep 16, 2026, 09:08 PM UTC

   The Auth0 Engineering has confirmed that the FGA service has been recovered. Error rates on affected environments have subsided, and impacted customers should observe service restoration at this time. After monitoring the environment to ensure service stability, we're considering this incident resolved. A root cause analysis (RCA) will be posted here within 7 business days. We sincerely apologize for the impact this had on you and your users.

5. postmortem Sep 24, 2026, 01:19 PM UTC

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

Read the full incident report →

Started Feb 06, 2026, 08:38 PM UTC· resolved Feb 06, 2026, 09:20 PM UTC

1. investigating Feb 06, 2026, 09:47 PM UTC

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

2. resolved Feb 06, 2026, 09:52 PM UTC

   This issue has now been resolved. Impact from this event affected multiple Auth0 services, however User Authentication was not impacted. Our investigation determined that a recent deployment inadvertently impacted multiple services and pages. We reverted to a previous version in order to mitigate the issue. After monitoring the environment to ensure stability, we've confirmed that our services are 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.

Read the full incident report →

Started Nov 18, 2025, 01:00 PM UTC· resolved Nov 18, 2025, 02:42 PM UTC

1. monitoring Nov 18, 2025, 02:23 PM UTC

   We're facing an incident with an upstream provider causing the FGA Dashboard, Playground and Docs to be inaccessible. The core APIs are not affected and it should still be possible to get tokens and interact with the API.

2. resolved Nov 18, 2025, 02:39 PM UTC

   The incident upstream has been resolved and the FGA Dashboard, Docs and Playground are back online.

3. postmortem Nov 25, 2025, 02:21 AM UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20251118\_Global\_Edge\_Provider\_Outage\_Impacting\_FGA-US-1\_Environment.pdf](https://cdn.auth0.com/blog/20251118_Global_Edge_Provider_Outage_Impacting_FGA-US-1_Environment.pdf)

Read the full incident report →

Started Oct 20, 2025, 06:57 AM UTC· resolved Oct 20, 2025, 04:20 PM UTC

1. identified Oct 20, 2025, 10:21 AM UTC

   On October 20, 2025, our Engineering team identified and reviewed an issue which impacted FGA US-1 core services ***Please note****: This specifically impacted those customer environments which are hosted on the US east coast. Our cloud provider has confirmed that they have applied mitigation actions and our Engineering team is observing recovery from this issue. We will provide a final confirmation here once our cloud provider has declared that this has been fully remediated.

2. monitoring Oct 20, 2025, 10:23 AM UTC

   Our Engineering team is monitoring recovery of all services for impacted customers.

3. monitoring Oct 20, 2025, 11:32 AM UTC

   We are continuing to monitor and the majority of services for impacted customers is in full recovery. We will post an additional update here in 30 minutes.

4. monitoring Oct 20, 2025, 11:56 AM UTC

   We have observed recovery for the majority of our customers, however our cloud provider is continuing to work towards official complete restoration of all services. We will monitor this issue for the next several hours and confirm here once they have marked this completely resolved.

5. monitoring Oct 20, 2025, 03:14 PM UTC

   Our cloud provider has noted that some network errors are persisting and some services may continue to experience impact. We are still observing recovery for the vast majority of our customers and we will continue to monitor this issue over the next several hours.

6. resolved Oct 20, 2025, 04:20 PM UTC

   Services have been restored. We will continue to monitor the environment to ensure the issue does not reoccur. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you.

7. postmortem Nov 03, 2025, 09:59 PM UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20251020\_Error\_Rates\_from\_Cloud\_Provider\_Impacting\_Customers\_for\_FGAUS1.pdf](https://cdn.auth0.com/blog/20251020_Error_Rates_from_Cloud_Provider_Impacting_Customers_for_FGAUS1.pdf)

Read the full incident report →

Started Sep 26, 2025, 06:23 PM UTC· resolved Sep 26, 2025, 06:41 PM UTC

1. investigating Sep 26, 2025, 06:34 PM UTC

   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.

2. monitoring Sep 26, 2025, 06:39 PM UTC

   We experienced high rate of errors and heightened latency for requests in FGA US-1 from approximately 14:07 to 14:09 UTC. We're observing recovery now and our engineering team continues to monitor this issue.

3. resolved Sep 26, 2025, 06:55 PM UTC

   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.

Read the full incident report →

Started Aug 21, 2025, 07:45 PM UTC· resolved Aug 21, 2025, 08:09 PM UTC

1. identified Aug 21, 2025, 07:46 PM UTC

   We have identified an issue that impacted network traffic for customers, specifically within US localities. Our Edge Provider was experiencing an issue from one of their Virginia based colocations and they are working to mitigate this urgently. We will provide additional updates in approximately 15 minutes

2. identified Aug 21, 2025, 07:48 PM UTC

   Our Engineering team is continuing to review this issue and we will post additional updates here shortly.

3. monitoring Aug 21, 2025, 07:52 PM UTC

   Error rates have subsided and our team is monitoring.

4. resolved Aug 21, 2025, 08:09 PM UTC

   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.

5. postmortem Sep 03, 2025, 10:08 PM UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250821\_Edge\_Provider\_Colocation\_Failure\_Impacting\_US\_Traffic.pdf](https://cdn.auth0.com/blog/20250821_Edge_Provider_Colocation_Failure_Impacting_US_Traffic.pdf)

Read the full incident report →

Started Mar 12, 2025, 08:11 PM UTC· resolved Mar 12, 2025, 08:14 PM UTC

1. identified Mar 12, 2025, 08:52 PM UTC

   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.

2. resolved Mar 12, 2025, 08:54 PM UTC

   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.

3. postmortem Mar 25, 2025, 04:06 PM UTC

   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)

Read the full incident report →

Started Jan 29, 2025, 10:55 AM UTC· resolved Jan 29, 2025, 11:15 AM UTC

1. investigating Jan 29, 2025, 11:01 AM UTC

   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.

2. monitoring Jan 29, 2025, 11:11 AM UTC

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

3. resolved Jan 29, 2025, 11:16 AM UTC

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

4. postmortem Jan 30, 2025, 05:12 PM UTC

   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.

Read the full incident report →

Started Jan 08, 2025, 02:20 PM UTC· resolved Jan 08, 2025, 04:06 PM UTC

1. investigating Jan 08, 2025, 02:22 PM UTC

   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.

2. investigating Jan 08, 2025, 02:27 PM UTC

   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.

3. identified Jan 08, 2025, 02:37 PM UTC

   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.

4. identified Jan 08, 2025, 02:59 PM UTC

   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.

5. monitoring Jan 08, 2025, 03:55 PM UTC

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

6. resolved Jan 08, 2025, 04:07 PM UTC

   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.

7. postmortem Jan 22, 2025, 11:57 PM UTC

   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)

Read the full incident report →

Started Jan 08, 2025, 01:53 PM UTC· resolved Jan 08, 2025, 04:10 PM UTC

1. identified Jan 08, 2025, 04:16 PM UTC

   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.

2. resolved Jan 08, 2025, 04:16 PM UTC

   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.

3. postmortem Jan 22, 2025, 11:57 PM UTC

   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)

Read the full incident report →

Started Dec 19, 2024, 09:58 PM UTC· resolved Dec 19, 2024, 11:00 PM UTC

1. investigating Dec 19, 2024, 10:09 PM UTC

   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.

2. investigating Dec 19, 2024, 10:28 PM UTC

   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.

3. monitoring Dec 19, 2024, 10:39 PM UTC

   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.

4. resolved Dec 19, 2024, 11:01 PM UTC

   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.

5. postmortem Jan 01, 2025, 07:54 PM UTC

   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)

Read the full incident report →

Started Nov 11, 2024, 06:30 PM UTC· resolved Nov 11, 2024, 06:33 PM UTC

1. identified Nov 11, 2024, 06:57 PM UTC

   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.

2. resolved Nov 11, 2024, 06:58 PM UTC

   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.

3. postmortem Nov 25, 2024, 01:13 PM UTC

   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)

Read the full incident report →

Started Oct 31, 2024, 03:59 PM UTC· resolved Oct 31, 2024, 04:04 PM UTC

1. identified Nov 05, 2024, 07:34 PM UTC

   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.

2. resolved Nov 05, 2024, 07:35 PM UTC

   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.

3. postmortem Nov 13, 2024, 05:37 PM UTC

   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)

Read the full incident report →

Started Oct 31, 2024, 01:29 PM UTC· resolved Oct 31, 2024, 03:15 PM UTC

1. investigating Oct 31, 2024, 01:32 PM UTC

   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.

2. identified Oct 31, 2024, 01:42 PM UTC

   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.

3. identified Oct 31, 2024, 01:59 PM UTC

   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.

4. identified Oct 31, 2024, 02:16 PM UTC

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

5. monitoring Oct 31, 2024, 02:19 PM UTC

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

6. resolved Oct 31, 2024, 03:16 PM UTC

   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.

7. postmortem Nov 13, 2024, 05:36 PM UTC

   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)

Read the full incident report →