Atlassian Developer Status

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.

If your app is impacted by this issue, the 429 response will contain the following headers:

X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0

Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly.

Our teams are investigating this issue with urgency, and we will provide an update within two hours.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers.

We will continue to share additional updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

Investigating: We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

Identified: We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

Identified: After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability.

We will share further updates within the next 8 hours, or sooner if there are any major developments.

Identified: Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

Investigating: We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted.