История сбоев Atlassian Developer

1. 2 сентября 2026 г. в 03:09 UTCinvestigating

   Мы расследуем сообщения о том, что запросы на установку разработчика Forge периодически терпят неудачу с сообщением «InstallationRequestFailedError». Мы поделимся дополнительной информацией в течение 1 часа или раньше.

2. 2 сентября 2026 г. в 03:17 UTCresolved

   Мы определили причину проблемы, влияющей на запросы на установку, и внедрили исправление. Теперь проблема решена, и сервис работает нормально для всех пострадавших клиентов.

Автоматический перевод официального обновления инцидента.

1. 25 августа 2026 г. в 10:58 UTCmonitoring

   Для некоторых приложений Marketplace было успешно развернуто исправление проблемы, затрагивающей запланированные триггеры (5-минутных интервалов). Мы продолжаем следить за ситуацией и должны быть полностью восстановлены в ближайшее время. Мы должны быть в состоянии предоставить больше обновлений за один час.

2. 25 августа 2026 г. в 11:11 UTCresolved

   25 августа 2026 года, между 08:12 UTC и 11:03 UTC, некоторые приложения Marketplace, возможно, испытали запланированные триггеры (5-минутных интервалов), которые не работают, как ожидалось. В настоящее время проблема решена, и 5-минутные запланированные триггеры работают нормально для всех клиентов.

Автоматический перевод официального обновления инцидента.

1. 3 августа 2026 г. в 03:26 UTCinvestigating

   Наша команда знает о проблеме, которая повлияла на возможность установки, удаления или управления интегрированными приложениями Forge и OAuth 2.0 между 2026-08-03 01:47 UTC и 02:29 UTC. Приложения, которые уже были установлены, должны были продолжать работать как обычно во время этого окна удара. Мы считаем, что сейчас мы исправили эту проблему и следим за текущим воздействием. Мы приносим извинения за любые неудобства, которые это могло вызвать.

2. 3 августа 2026 г. в 03:37 UTCresolved

   Мы подтвердили, что проблемы, связанные с установкой, удалением и управлением приложениями Forge и OAuth 2.0, теперь должны быть полностью решены.

Автоматический перевод официального обновления инцидента.

1. 13 июля 2026 г. в 15:48 UTCinvestigating

   Страницы партнеров Marketplace недоступны. Партнеры не могут получить доступ к панели инструментов и интерфейсам управления, испытывая тайм-ауты при попытке загрузить эти страницы. Все связанные с партнером функциональные возможности затронуты. Ведется расследование основной причины. Следующие сообщения будут отправлены через 60 минут или после значительного прогресса.

2. 13 июля 2026 г. в 17:17 UTCmonitoring

   Проблема решена, и сервисы теперь работают нормально для всех пострадавших клиентов. Мы продолжим внимательно следить, чтобы подтвердить стабильность.

3. 13 июля 2026 г. в 17:46 UTCresolved

   13 июля 2026 года партнерские операции, возможно, столкнулись с некоторыми перебоями в обслуживании. Теперь проблема решена, и сервис работает нормально для всех пострадавших клиентов.

Автоматический перевод официального обновления инцидента.

1. 30 июня 2026 г. в 02:45 UTCinvestigating

   Мы знаем, что некоторые клиенты, которые используют Time Tracker для Jira Cloud и DC, были неправильно уведомлены о переходе приложения на бесплатную или пробную подписку. Наша команда изучает этот вопрос в срочном порядке, и мы предпринимаем шаги для обеспечения информированности пострадавших клиентов. От клиентов, которые неправильно получили эти электронные письма, не требуется никаких действий. Мы приносим извинения за любые неудобства, которые это могло вызвать.

2. 2 июля 2026 г. в 04:43 UTCresolved

   Все клиенты, которые ранее получали неправильные уведомления о Time Tracker для Jira Cloud и DC, должны были получать корректирующие сообщения в это время. Сейчас мы решаем этот вопрос.

Автоматический перевод официального обновления инцидента.

1. 26 июня 2026 г. в 14:32 UTCidentified

   Мы определили источник проблем с производительностью обслуживания, влияющих на ваши услуги удаленных приложений. Наша команда инициировала восстановление и активно следит за восстановлением. Мы предоставим следующее обновление в течение следующего часа.

2. 26 июня 2026 г. в 15:28 UTCidentified

   Наша команда применила смягчение, и мы видим восстановление. Мы будем продолжать делиться дополнительными обновлениями по мере поступления дополнительной информации.

3. 26 июня 2026 г. в 19:43 UTCidentified

   Наша команда продолжает следить за восстановлением, и мы поделимся дополнительными обновлениями здесь по мере поступления дополнительной информации.

4. 26 июня 2026 г. в 21:24 UTCmonitoring

   Проблема решена, и сервисы теперь работают нормально для всех пострадавших клиентов. Мы продолжим внимательно следить, чтобы подтвердить стабильность.

5. 26 июня 2026 г. в 21:39 UTCresolved

   26 июня 2026 года некоторые клиенты, возможно, испытали ухудшение производительности с удаленными приложениями Forge, сталкивающимися с проблемами ограничения скорости. Теперь проблема решена, и сервис работает нормально для всех пострадавших клиентов.

Автоматический перевод официального обновления инцидента.

1. 10 июня 2026 г. в 04:55 UTCinvestigating

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. 10 июня 2026 г. в 05:39 UTCidentified

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. 10 июня 2026 г. в 06:14 UTCmonitoring

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. 10 июня 2026 г. в 06:31 UTCresolved

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

1. 26 мая 2026 г. в 11:58 UTCinvestigating

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. 26 мая 2026 г. в 11:58 UTCinvestigating

   We are actively investigating an issue affecting the editing macros in Confluence Cloud editor. Our team is working to identify the root cause. We will provide an update within approximately one hour.

3. 26 мая 2026 г. в 13:55 UTCresolved

   Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.

1. 20 мая 2026 г. в 12:06 UTCidentified

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

2. 20 мая 2026 г. в 14:14 UTCresolved

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

1. 20 мая 2026 г. в 10:16 UTCresolved

   Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps. The feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability. We apologise for any confusion this may have caused.

1. 14 мая 2026 г. в 21:04 UTCidentified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inaccessibility for Developer and Marketplace service desks. We will continue to share additional updates here as more information is available.

2. 14 мая 2026 г. в 21:20 UTCmonitoring

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

3. 14 мая 2026 г. в 21:35 UTCresolved

   On May 14, 2026, Developer and Marketplace service desks were inaccessible for affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 14 мая 2026 г. в 05:11 UTCidentified

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

2. 14 мая 2026 г. в 05:24 UTCidentified

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

3. 14 мая 2026 г. в 05:34 UTCidentified

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

4. 14 мая 2026 г. в 05:43 UTCmonitoring

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

5. 14 мая 2026 г. в 06:40 UTCmonitoring

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

6. 14 мая 2026 г. в 06:41 UTCmonitoring

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

7. 14 мая 2026 г. в 06:49 UTCresolved

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

1. 12 мая 2026 г. в 15:50 UTCidentified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience intermittent failures with forge invocations for some applications. We will continue to share additional updates here as more information is available.

2. 12 мая 2026 г. в 16:57 UTCidentified

   We are seeing improvements in intermittent failures with forge invocations for some applications. Our team continues to work diligently on full mitigation, and we will continue to share additional updates as more information becomes available.

3. 12 мая 2026 г. в 17:17 UTCmonitoring

   Intermittent failures with forge invocations for some applications have been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

4. 12 мая 2026 г. в 17:40 UTCresolved

   On May 12, 2026, some users in US East region may have experienced intermittent failures with forge invocations for some applications. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 12 мая 2026 г. в 14:03 UTCinvestigating

   We are aware of delays in Webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU-West region. Some partners may experience delayed or queued Webhook Events. Our teams are investigating the root cause, and we will provide further updates within the next 1 hour.

2. 12 мая 2026 г. в 15:00 UTCinvestigating

   Our teams are still investigating the root cause, and we will provide further updates within the next 2 hours.

3. 12 мая 2026 г. в 16:27 UTCidentified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience delayed or queued webhook events. We will continue to share additional updates here as more information is available.

4. 12 мая 2026 г. в 17:52 UTCmonitoring

   Delayed or queued webhook events issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

5. 12 мая 2026 г. в 18:11 UTCresolved

   On May 12, 2026, some users in EU West region may have experienced delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 11 мая 2026 г. в 14:24 UTCidentified

   We are aware of delays in webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU west region. Some partners may experience delayed or queued webhook events. Our team has identified the root cause and has taken action to mitigate the issue. We will continue to monitor and provide updates as the situation progresses.

2. 11 мая 2026 г. в 14:48 UTCidentified

   Webhook event delivery in the EU West region has recovered and is operating normally. However, we are now seeing reports of similar delays in the US East region. Our team is actively investigating and working to resolve this. We will continue to monitor and provide further updates.

3. 11 мая 2026 г. в 15:45 UTCidentified

   Our team has applied mitigation and is seeing improvement in US East region. Next update will be provided in one hour.

4. 11 мая 2026 г. в 16:42 UTCidentified

   Our team continues to see improvements in US East region with delayed or queued webhook events declining. Next update will be provided in 90 minutes.

5. 11 мая 2026 г. в 18:00 UTCmonitoring

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

6. 11 мая 2026 г. в 18:16 UTCresolved

   On May 11, 2026, users in EU West and US East regions may have experienced performance degradation with delayed or queued webhook events. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 8 мая 2026 г. в 04:10 UTCinvestigating

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. 8 мая 2026 г. в 04:10 UTCidentified

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. 8 мая 2026 г. в 04:10 UTCidentified

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

4. 8 мая 2026 г. в 04:10 UTCidentified

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

5. 8 мая 2026 г. в 05:53 UTCmonitoring

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

6. 8 мая 2026 г. в 08:03 UTCmonitoring

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

7. 8 мая 2026 г. в 11:12 UTCmonitoring

   Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.

8. 8 мая 2026 г. в 19:45 UTCresolved

   On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

9. 20 мая 2026 г. в 06:58 UTCpostmortem

   All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation. * Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline. * At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows. * At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00. * By 18:48, Automation had processed their backlog of events that were created while processing **Automation** Between 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed. Beginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded. **Jira and Jira Service Management** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident. Jira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded. **Confluence** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation. The underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed. Between 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync. **Bitbucket and Pipelines** Between 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident. Automatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits. At approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes. **Identity Services** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident. The impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays. After the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services. We are prioritizing improvements that will: * **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions. * **Strengthen recovery handling** so replayed events can be processed more quickly. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support.

1. 5 мая 2026 г. в 17:40 UTCinvestigating

   We are actively investigating reports of performance degradation affecting Forge webhook delivery in the US East region. We will share updates here as more information is available.

2. 5 мая 2026 г. в 18:58 UTCidentified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available.

3. 5 мая 2026 г. в 20:37 UTCidentified

   Our teams have identified the cause of the issue and are continuing to work on mitigations. We continue to see signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available.

4. 5 мая 2026 г. в 22:34 UTCresolved

   On Tuesday, May 5, 2026, some Forge users may have experienced performance delays in webhook delivery in the US East region. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 30 апреля 2026 г. в 08:59 UTCinvestigating

   We are investigating reports of delays in webhook delivery. Customers may experience intermittent delays when receiving webhooks. Our engineering teams are actively investigating and working to resolve the issue. We will provide updates as more information becomes available.

2. 30 апреля 2026 г. в 10:05 UTCidentified

   We have identified the cause of the delayed Jira webhook delivery and are deploying a fix. We will continue to provide updates as more information becomes available.

3. 30 апреля 2026 г. в 13:36 UTCmonitoring

   A fix has been deployed to address the intermittent delays in Jira webhook delivery. We are actively monitoring the situation to confirm full recovery. We will continue to provide updates as available.

4. 30 апреля 2026 г. в 14:56 UTCresolved

   The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally.

1. 28 апреля 2026 г. в 18:28 UTCinvestigating

   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.

2. 28 апреля 2026 г. в 18:34 UTCinvestigating

   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.

3. 28 апреля 2026 г. в 20:16 UTCidentified

   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.

4. 28 апреля 2026 г. в 21:34 UTCmonitoring

   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.

5. 28 апреля 2026 г. в 21:50 UTCresolved

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

1. 22 апреля 2026 г. в 06:57 UTCinvestigating

   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.

2. 22 апреля 2026 г. в 08:53 UTCidentified

   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.

3. 22 апреля 2026 г. в 16:21 UTCidentified

   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.

4. 22 апреля 2026 г. в 23:29 UTCidentified

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

5. 23 апреля 2026 г. в 15:27 UTCmonitoring

   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.

6. 23 апреля 2026 г. в 16:14 UTCresolved

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