We've applied the necessary configuration changes to address ‌service instability and are seeing signs of a gradual recovery with services and throughput.

Update timeline

1. identified Jul 15, 2026, 02:00 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Jul 15, 2026, 02:21 PM UTC

   We're investigating an issue impacting the API Analytics service for a subset of customers in the US region, which may result in intermittent issues when using the API Analytics product. We’re working on implementing a fix to restore normal service. We'll provide an update in 30 minutes or sooner if more information becomes available.

3. monitoring Jul 15, 2026, 02:46 PM UTC

   The implemented fix didn’t resolve the issue, and we’re working on identifying the underlying cause while continuing to work toward restoring normal service. We'll provide another update in 30 minutes, or sooner if more information becomes available.

4. monitoring Jul 15, 2026, 03:16 PM UTC

   We're continuing our investigation and are testing a change to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 15, 2026, 03:44 PM UTC

   We've implemented a change to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 15, 2026, 04:13 PM UTC

   We've completed a targeted configuration change to address this issue and we're monitoring the results. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Jul 15, 2026, 04:42 PM UTC

   We've identified that the configuration change we implemented hasn't fully restored service. We're now deploying an updated configuration to allow service instances to stabilize and begin receiving traffic normally. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Jul 15, 2026, 05:10 PM UTC

   We're continuing to investigate. A configuration update intended to stabilize service instances encountered a deployment error and is being retried. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Jul 15, 2026, 05:39 PM UTC

   We're continuing to investigate. Our most recent configuration change hasn't improved service stability, and we're now reverting those changes while pursuing an alternative path to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Jul 15, 2026, 06:09 PM UTC

    We're continuing to investigate. In addition to reverting our most recent configuration changes, we're investigating a potential underlying network routing issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. monitoring Jul 15, 2026, 06:42 PM UTC

    We're continuing to investigate, and engaged additional subject matter experts to assist with diagnosing the underlying network routing issue. In parallel, we're updating a configuration to scale service capacity and remove a dependency that may be contributing to the instability. We'll provide an update in 60 minutes or sooner if additional information becomes available.

12. monitoring Jul 15, 2026, 07:36 PM UTC

    We're continuing to investigate the underlying trigger of this issue. Based on our latest analysis, we're implementing an additional mitigation that updates service health check behavior while maintaining previously applied routing changes. We're monitoring the rollout and validating whether these changes restore service stability. We'll provide an update in 60 minutes or sooner if additional information becomes available.

13. monitoring Jul 15, 2026, 08:36 PM UTC

    We're continuing to investigate the underlying cause of this issue. Based on our latest findings, we're deploying an updated service configuration that adjusts health check behavior while also removing an external dependency from the request path to improve service stability. We also continue to monitor the deployment and validate service recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

14. monitoring Jul 15, 2026, 09:37 PM UTC

    Our investigation is ongoing, and we are actively validating multiple mitigation steps. We have identified inconsistent service startup behavior and are deploying configuration adjustments to improve application health while continuing to investigate the underlying trigger. We are monitoring the rollout and evaluating service recovery as the changes propagate. We'll provide an update in 60 minutes or sooner if additional information becomes available.

15. monitoring Jul 15, 2026, 10:53 PM UTC

    We've completed a deployment of the latest fix and are observing recovery as application instances continue returning to service. Our teams are validating that sufficient service capacity has been restored and are monitoring live traffic to confirm normal processing. We'll provide an update in 60 minutes or sooner if additional information becomes available.

16. monitoring Jul 16, 2026, 12:07 AM UTC

    We're continuing to investigate the service issue affecting Analytics customers in the US region. Our teams identified additional infrastructure constraints affecting service stability. We're now rolling back to a previous stable configuration version. We'll provide an update in 60 minutes or sooner if additional information becomes available.

17. monitoring Jul 16, 2026, 01:00 AM UTC

    We're continuing to work on restoring full-service stability for Analytics customers in the US region. We completed a rollback to a previous stable software version. Early results show improvement. We're now scaling additional capacity to further stabilize the service and are closely monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

18. monitoring Jul 16, 2026, 02:23 AM UTC

    Our investigation into the API Manager (APIM) ingestion functionality issue remains ongoing, and we have no new details to report at this time. We'll post our next update when a significant development occurs or as soon as more information becomes available.

19. monitoring Jul 16, 2026, 03:47 AM UTC

    We continue to investigate an issue affecting API Analytics services. Our teams have identified that delays are originating within the network layer rather than the application itself, and are working on a resolution. We're seeing signs of improvement and will provide the next update within 60 minutes, or as soon as more information is available.

20. monitoring Jul 16, 2026, 04:35 AM UTC

    We've applied the necessary configuration changes to address ‌service instability and are seeing signs of a gradual recovery with services and throughput. We'll continue to monitor service stability closely and provide the next update as soon as more information becomes available.