Atlassian Developer incident

Forge usage and charges data is missing from the developer console

Minor Resolved View vendor source →

Atlassian Developer experienced a minor incident on December 16, 2025 affecting Developer console, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Dec 16, 2025, 05:47 AM UTC
Resolved
Dec 17, 2025, 06:07 AM UTC
Duration
1d
Detected by Pingoru
Dec 16, 2025, 05:47 AM UTC

Affected components

Developer console

Update timeline

  1. identified Dec 16, 2025, 05:47 AM UTC

    We have identified an issue with the Forge Developer Console, which is not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.

  2. identified Dec 16, 2025, 05:47 AM UTC

    We have identified an issue with the Forge Developer Console not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.

  3. monitoring Dec 16, 2025, 04:14 PM UTC

    The issue affecting the display of data on the Usage and Charges page in the Forge Developer Console has been largely resolved. All charge elements, except for Forge Compute, are now displaying accurate values. We are actively working to resolve the remaining issue with Forge Compute. We will provide another update once this final issue has been fully mitigated.

  4. identified Dec 16, 2025, 04:14 PM UTC

    The issue affecting the display of data on the Usage and Charges page in the Forge Developer Console has been largely resolved. All charge elements, except for Forge Compute, are now displaying accurate values. We are actively working to resolve the remaining issue with Forge Compute. We will provide another update once this final issue has been fully mitigated.

  5. resolved Dec 17, 2025, 06:07 AM UTC

    The issue is completely resolved and Developer Console is now displaying all the usage metrics correctly. We apologize for any inconvenience this may have caused.