Vendor reports: degradedResolved · vendor status “resolved”Official status API

Degraded performance of Forge trigger

Reported by Atlassian Developer · Developer Tools & CI/CD · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Apr 28, 2026, 18:28 UTC
Vendor's clock
Resolved
Apr 28, 2026, 21:50 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 22 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Atlassian Developer reports degraded: "Degraded performance of Forge trigger".[E1, E2]
  • The vendor marked it resolved at 2026-04-28 21:50 UTC.[E3, E7]

Affected products and regions

  • Components: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-04-28 21:50 UTC · summary s1, evidence a5f68a7d1abb7c63

Evidence (7)
  1. E1Atlassian Developer reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Degraded performance of Forge trigger". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-04-28 18:28 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-04-28 21:50 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Bitbucket Cloud APIs, App listing management, App Deployment, App listings, Confluence Cloud APIs, Artifactory (Maven repository), Atlassian Support contact form, App pricing, Jira Cloud APIs, Create and manage apps, Developer community, Developer documentation, Developer service desk, App submissions, Authentication and user management, Product Events, Marketplace service desk, User APIs, Category landing pages, Forge App Installation, Webhooks, Evaluations and purchases, Atlassian Support, Forge CDN (Custom UI), In-product Marketplace and app installation (Cloud), Forge Function Invocation, Web Triggers, Vulnerability management [AMS], In-product Marketplace and app installation (Server), aui-cdn.atlassian.com, Notifications, Forge App Logs, Private listings, Forge App Monitoring, Reporting APIs and dashboards, Developer console, Search, Forge direct app distribution, Vendor management, Hosted storage, Vendor Home Page, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Atlassian Developer is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Apr 28, 2026, 18:28 UTCVendor-reported startVendor time
  2. Apr 28, 2026, 21:50 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.