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

Degraded performance of forge invocations

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

Official source (opens in a new tab)
Vendor start
May 12, 2026, 15:50 UTC
Vendor's clock
Resolved
May 12, 2026, 17:40 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 50 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 invocations".[E1, E2]
  • The vendor marked it resolved at 2026-05-12 17:40 UTC.[E3, E7]

Affected products and regions

  • Components: Forge Function Invocation.[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-05-12 17:40 UTC · summary s1, evidence 8702768f90b18438

Evidence (7)
  1. E1Atlassian Developer reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Degraded performance of forge invocations". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-12 15:50 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Forge Function Invocation. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-05-12 17:40 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Forge Function Invocation

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. May 12, 2026, 15:50 UTCVendor-reported startVendor time
  2. May 12, 2026, 17:40 UTCVendor-reported resolutionVendor time

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