Appen Outage History

Appen is up right now

Appen had 16 outages in the last 2 years totaling 31h 43m of downtime — averaging 0.7 incidents per month.

There were 16 Appen outages since July 12, 2024 totaling 31h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.appen.com

Critical September 11, 2025

test-incident

Detected by Pingoru
Sep 11, 2025, 09:54 AM UTC
Resolved
Sep 11, 2025, 09:58 AM UTC
Duration
3m
Timeline · 2 updates
  1. investigating Sep 11, 2025, 09:54 AM UTC

    test

  2. resolved Sep 11, 2025, 09:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 11, 2025

test

Detected by Pingoru
Sep 11, 2025, 09:30 AM UTC
Resolved
Sep 11, 2025, 09:34 AM UTC
Duration
3m
Timeline · 2 updates
  1. investigating Sep 11, 2025, 09:30 AM UTC

    test

  2. resolved Sep 11, 2025, 09:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 11, 2025

Test-issue

Detected by Pingoru
Sep 11, 2025, 09:03 AM UTC
Resolved
Sep 11, 2025, 09:04 AM UTC
Duration
1m
Timeline · 3 updates
  1. investigating Sep 11, 2025, 09:03 AM UTC

    Test issue created

  2. investigating Sep 11, 2025, 09:04 AM UTC

    New comment on Jira issue SPTT-29: comment test

  3. resolved Sep 11, 2025, 09:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 9, 2025

test 21

Detected by Pingoru
Sep 09, 2025, 02:16 PM UTC
Resolved
Sep 09, 2025, 02:28 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Sep 09, 2025, 02:16 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 09, 2025, 02:16 PM UTC

    New comment on Jira issue SPTT-28: test

  3. resolved Sep 09, 2025, 02:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 9, 2025

test 20

Detected by Pingoru
Sep 09, 2025, 02:10 PM UTC
Resolved
Sep 09, 2025, 02:11 PM UTC
Duration
27s
Timeline · 3 updates
  1. investigating Sep 09, 2025, 02:10 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 09, 2025, 02:11 PM UTC

    New comment on Jira issue SPTT-27: test

  3. resolved Sep 09, 2025, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 9, 2025

test 19

Detected by Pingoru
Sep 09, 2025, 01:54 PM UTC
Resolved
Sep 09, 2025, 02:07 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Sep 09, 2025, 01:54 PM UTC

    test

  2. investigating Sep 09, 2025, 01:55 PM UTC

    New comment on Jira issue SPTT-26: test comment

  3. resolved Sep 09, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 9, 2025

test-17

Detected by Pingoru
Sep 09, 2025, 01:47 PM UTC
Resolved
Sep 09, 2025, 02:29 PM UTC
Duration
42m
Timeline · 4 updates
  1. investigating Sep 09, 2025, 01:47 PM UTC

    test

  2. investigating Sep 09, 2025, 01:47 PM UTC

    New comment on Jira issue SPTT-24: test comment

  3. investigating Sep 09, 2025, 01:48 PM UTC

    New comment on Jira issue SPTT-24: comment

  4. resolved Sep 09, 2025, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 2, 2025

test-15

Detected by Pingoru
Sep 02, 2025, 11:20 AM UTC
Resolved
Sep 02, 2025, 02:06 PM UTC
Duration
2h 45m
Timeline · 2 updates
  1. investigating Sep 02, 2025, 11:20 AM UTC

    test-15

  2. resolved Sep 02, 2025, 02:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 2, 2025

test 14

Detected by Pingoru
Sep 02, 2025, 11:17 AM UTC
Resolved
Sep 02, 2025, 02:06 PM UTC
Duration
2h 48m
Timeline · 2 updates
  1. investigating Sep 02, 2025, 11:17 AM UTC

    test 14

  2. resolved Sep 02, 2025, 02:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 2, 2025

test 10

Detected by Pingoru
Sep 02, 2025, 11:04 AM UTC
Resolved
Sep 02, 2025, 02:07 PM UTC
Duration
3h 2m
Timeline · 2 updates
  1. investigating Sep 02, 2025, 11:04 AM UTC

    test

  2. resolved Sep 02, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 2, 2025

test 777

Detected by Pingoru
Sep 02, 2025, 10:54 AM UTC
Resolved
Sep 02, 2025, 02:07 PM UTC
Duration
3h 12m
Timeline · 2 updates
  1. investigating Sep 02, 2025, 10:54 AM UTC

    test

  2. resolved Sep 02, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 2, 2025

test8

Detected by Pingoru
Sep 02, 2025, 10:53 AM UTC
Resolved
Sep 02, 2025, 02:07 PM UTC
Duration
3h 14m
Timeline · 2 updates
  1. investigating Sep 02, 2025, 10:53 AM UTC

    test

  2. resolved Sep 02, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 11, 2024

Issues with Reports and Dashboards

Detected by Pingoru
Nov 11, 2024, 09:55 PM UTC
Resolved
Nov 12, 2024, 12:56 AM UTC
Duration
3h
Timeline · 4 updates
  1. investigating Nov 11, 2024, 09:55 PM UTC

    We are currently experiencing issues with reports and dashboards. The team is actively investigating.

  2. identified Nov 11, 2024, 10:11 PM UTC

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

  3. monitoring Nov 11, 2024, 10:24 PM UTC

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

  4. resolved Nov 12, 2024, 12:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 7, 2024

Platform Degradation

Detected by Pingoru
Nov 07, 2024, 12:46 AM UTC
Resolved
Nov 07, 2024, 02:39 AM UTC
Duration
1h 52m
Timeline · 4 updates
  1. investigating Nov 07, 2024, 12:46 AM UTC

    We are currently experiencing platform-wide degradation and errors. The team is actively investigating the issue to resolve it.

  2. identified Nov 07, 2024, 02:12 AM UTC

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

  3. monitoring Nov 07, 2024, 02:32 AM UTC

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

  4. resolved Nov 07, 2024, 02:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 15, 2024

Server Error

Detected by Pingoru
Aug 15, 2024, 11:24 PM UTC
Resolved
Aug 16, 2024, 03:13 AM UTC
Duration
3h 49m
Timeline · 6 updates
  1. investigating Aug 15, 2024, 11:24 PM UTC

    We are currently investigating a server error affecting internal work links. Our team is working diligently to resolve the issue. Thank you for your patience and understanding.

  2. investigating Aug 15, 2024, 11:56 PM UTC

    We are actively investigating the issue and will provide updates as soon as we have more information. Thank you for your patience.

  3. investigating Aug 16, 2024, 01:02 AM UTC

    We are actively investigating the issue and will provide updates once we have more information. Thank you for your patience.

  4. identified Aug 16, 2024, 02:16 AM UTC

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

  5. monitoring Aug 16, 2024, 03:03 AM UTC

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

  6. resolved Aug 16, 2024, 03:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 12, 2024

Unit Reservation Cleanup Delay

Detected by Pingoru
Jul 12, 2024, 02:46 PM UTC
Resolved
Jul 12, 2024, 09:25 PM UTC
Duration
6h 39m
Affected: Customer Portal and API
Timeline · 5 updates
  1. identified Jul 12, 2024, 02:46 PM UTC

    Dear Customers, We are experiencing an issue with unit reservations not being cleaned up promptly upon judgment submission. This may lead to an increased number of pending judgments and potentially affect the assignment of units to contributors. The issue has been identified and the team is currently working on it.

  2. identified Jul 12, 2024, 03:18 PM UTC

    it’s not happening to new judgments but it affects some previous judgments. The team is currently trying to recover previous judgements.

  3. identified Jul 12, 2024, 09:24 PM UTC

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

  4. identified Jul 12, 2024, 09:25 PM UTC

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

  5. resolved Jul 12, 2024, 09:25 PM UTC

    This incident has been resolved.

Read the full incident report →