AppFox Outage History

AppFox is up right now

AppFox had 9 outages in the last 2 years totaling 1386h 44m of downtime — averaging 0.4 incidents per month.

There were 9 AppFox outages since September 19, 2025 totaling 1386h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.appfox.io

Major February 6, 2026

Scheduled Triggers not working for Atlassian Forge apps

Detected by Pingoru
Feb 06, 2026, 10:19 AM UTC
Resolved
Feb 06, 2026, 11:59 AM UTC
Duration
1h 40m
Affected: Core App
Timeline · 3 updates
  1. investigating Feb 06, 2026, 10:19 AM UTC

    Atlassian are investigating an incident with Scheduled Triggers not working for Forge apps (see https://developer.status.atlassian.com/incidents/rlrntm2fw82b). The functionality of Compliance for Confluence Cloud may be affected as a result.

  2. identified Feb 06, 2026, 10:41 AM UTC

    Atlassian has updated their incident stating that "The issue is suspected to be related to a recent change that was deployed. The team is currently rolling back the changes."

  3. resolved Feb 06, 2026, 11:59 AM UTC

    Atlassian notify that their "engineering team identified the root cause and performed a rollback deployment to resolve the issue."

Read the full incident report →

Critical January 28, 2026

All apps affected by an incident on the Atlassian side affecting Forge functions

Detected by Pingoru
Jan 28, 2026, 05:10 PM UTC
Resolved
Jan 29, 2026, 09:02 AM UTC
Duration
15h 51m
Affected: Core AppCore AppCore AppCore App
Timeline · 4 updates
  1. investigating Jan 28, 2026, 05:10 PM UTC

    We are aware of an incident affecting all our apps, as well as apps from other vendors, which appears to be linked to Forge functions not working as expected on the Atlassian side. The issue has been reported to Atlassian, and we are waiting for a response.

  2. investigating Jan 28, 2026, 06:51 PM UTC

    Atlassian have acknowledged the incident, and are providing updates on the developer status page here: https://developer.status.atlassian.com/ We are continuing to work with them and are monitoring the situation.

  3. monitoring Jan 28, 2026, 07:04 PM UTC

    Atlassian have implemented a fix, and we are monitoring any further impacts.

  4. resolved Jan 29, 2026, 09:02 AM UTC

    On Wed 28th Jan, 19:20 UTC, Atlassian marked the incident as resolved. They explained that "On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. The issue has now been resolved, and the service is operating normally for all affected customers."

Read the full incident report →

Major January 7, 2026

Approval Quorum Issue

Detected by Pingoru
Jan 07, 2026, 10:42 AM UTC
Resolved
Jan 07, 2026, 02:29 PM UTC
Duration
3h 46m
Affected: Core App
Timeline · 5 updates
  1. investigating Jan 07, 2026, 10:42 AM UTC

    We are currently investigating an issue with Approval stages not transitioning correctly despite meeting the configured quorum requirements.

  2. identified Jan 07, 2026, 11:11 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 07, 2026, 11:32 AM UTC

    A fix is in the process of being deployed. If you are affected by this issue, you can click the Sync button on the workflow to trigger the transition.

  4. monitoring Jan 07, 2026, 11:43 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 07, 2026, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 28, 2025

Workflows for Confluence: Intermittent outage for some customers due to content delivery network cache issues

Detected by Pingoru
Nov 28, 2025, 09:41 AM UTC
Resolved
Nov 27, 2025, 05:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 28, 2025, 09:41 AM UTC

    Some customers experienced an outage of the Workflows for Confluence app; the app user interface would not load on several pages. This was caused by a stale cache issue on our content delivery network as part of a deployment on 27 Nov 2025 at 17:30. The stale cache has now been cleared and the incident is resolved.

Read the full incident report →

Major September 30, 2025

Approvals for Confluence and Workflows for Confluence: Partial outages

Detected by Pingoru
Sep 30, 2025, 08:30 AM UTC
Resolved
Sep 30, 2025, 02:26 PM UTC
Duration
5h 55m
Affected: Core AppCore App
Timeline · 6 updates
  1. identified Sep 30, 2025, 08:30 AM UTC

    We are currently investigating problems with Page Approvals on Approvals Cloud. We are observing the following problems: - Errors trying to load the byline on new pages with no page approval - On existing pages with page approvals, sometimes making decisions does not work - Cannot create/edit the settings of page approvals Section approvals is unaffected. We have identified the cause of this incident; some Atlassian endpoints we rely on have been removed. We are working with Atlassian to get this resolved.

  2. identified Sep 30, 2025, 09:00 AM UTC

    We have identified that Workflows is affected by the same issue. Currently, Page History is showing "No History" on pages where a Workflow history is expected. We are continuing to work on a resolution. edit: We have also identified issues with Approval Comments, Linked Published Pages, and Workflow Removal.

  3. identified Sep 30, 2025, 10:26 AM UTC

    We have deployed a fix for page approvals on Approvals for Confluence. We are continuing to work on a resolution for Workflows for Confluence to restore full functionality.

  4. identified Sep 30, 2025, 11:38 AM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Sep 30, 2025, 11:39 AM UTC

    We have released fixes for the issues with Workflows. We are now monitoring the changes in production.

  6. resolved Sep 30, 2025, 02:26 PM UTC

    This has been verified as fixed across multiple production sites.

Read the full incident report →

Minor September 19, 2025

Workflows for Confluence: Publish Content with Page Ancestry outage

Detected by Pingoru
Sep 19, 2025, 09:30 AM UTC
Resolved
Sep 19, 2025, 09:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 19, 2025, 09:43 AM UTC

    From 17:00 UTC on 17th September 2025, users of Workflows for Confluence experienced errors when attempting to use the Publish Content action with 'Clone Page Ancestry' enabled. As of 09:30 UTC on 19th September 2025, this issue has been resolved; Publish Content with Page Ancestry will now work as expected.

Read the full incident report →