Common Ninja Outage History

Common Ninja is up right now

Pingoru has recorded 3 incidents for Common Ninja: 0 in the last 12 months and 0 in the last 90 days.

Source: commonninja.statuspage.io

3incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Common Ninja in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 560 (0%)

Incidents, newest first

Major October 20, 2025 AWS Global Service Degradation 11h 45m API, Editor, Editor, Embed and 1 more

Started Oct 20, 2025, 02:44 PM UTC· resolved Oct 21, 2025, 02:30 AM UTC

  1. investigating Oct 20, 2025, 02:44 PM UTC

    Multiple Common Ninja services may experience degraded performance or temporary unavailability. AWS is currently experiencing increased error rates and latencies across multiple services in the US-EAST-1 (N. Virginia) region. This issue is affecting key services such as EC2, Lambda, RDS, SQS, and EventBridge, which may lead to intermittent issues or slow performance for Common Ninja users.

  2. investigating Oct 20, 2025, 02:44 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 20, 2025, 03:13 PM UTC

    AWS has shared an update regarding the ongoing network connectivity issues affecting multiple services in the US-EAST-1 (N. Virginia) region. According to AWS, the issue originated from within the EC2 internal network and continues to impact services such as DynamoDB, SQS, and Amazon Connect. AWS is actively investigating and implementing mitigations to restore full service. As a result, some Common Ninja services may still experience intermittent errors, latency, or degraded performance. We’re closely monitoring AWS’s progress and will continue to provide updates as more information becomes available. 👉 Follow official AWS updates here: https://status.aws.amazon.com/

  4. investigating Oct 20, 2025, 04:41 PM UTC

    We’re still monitoring the ongoing AWS outage. AWS is investigating a network issue within the EC2 internal network affecting multiple services. Some Common Ninja features may still experience intermittent issues. We’ll update again once AWS provides more details.

  5. investigating Oct 20, 2025, 05:19 PM UTC

    We are continuing to investigate this issue.

  6. investigating Oct 20, 2025, 06:34 PM UTC

    We are continuing to investigate this issue.

  7. resolved Oct 21, 2025, 04:18 AM UTC

    AWS has confirmed that the network connectivity issues in the US-EAST-1 (N. Virginia) region have been fully resolved. All affected AWS services, including EC2, DynamoDB, SQS, and Amazon Connect, have recovered, and Common Ninja systems are now operating normally. We’ll continue to monitor performance to ensure full stability, but no further impact is expected. Thank you for your patience and understanding during this incident 🙏

Read the full incident report →

Critical June 10, 2025 🚨 Heroku Platform Outage 8h 50m Editor, Editor, Embed, Dashboard

Started Jun 10, 2025, 04:09 PM UTC· resolved Jun 11, 2025, 01:00 AM UTC

  1. investigating Jun 10, 2025, 04:09 PM UTC

    We are currently experiencing an outage due to an issue with the Heroku platform. This affects several of our backend services, leading to degraded performance or inaccessibility of some features. The issue originates from Heroku's infrastructure (see Heroku Status Incident #2822, https://status.heroku.com/incidents/2822). Our engineering team is actively monitoring the situation and will provide updates as more information becomes available. We appreciate your patience and understanding.

  2. investigating Jun 10, 2025, 04:16 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 10, 2025, 06:19 PM UTC

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

  4. resolved Jun 11, 2025, 04:04 AM UTC

    This incident has been resolved.

Read the full incident report →