Accelo Outage History

Accelo is up right now

Pingoru has recorded 5 incidents for Accelo: 2 in the last 12 months and 0 in the last 90 days.

Source: status.accelo.com

5incidents recorded
2last 12 months
0last 90 days
7 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Accelo 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 202610 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 112 (0%)

Incidents, newest first

Notice July 29, 2026 Service Disruption: Technical Issue Affecting Emails Sent From Accelo 12h 47m

Started Jul 29, 2026, 12:43 AM UTC· resolved Jul 29, 2026, 01:30 PM UTC

  1. monitoring Jul 29, 2026, 12:43 AM UTC

    We want to inform you that there was an an issue affecting emails sent from Accelo. We have identified the root cause and the emails are now being delivered, however there may still be intermittent delivery issues until this is fully resolved. We appreciate your patience as we work with our provider to ensure complete stability. We apologize for the inconvenience and appreciate your patience. You can track live updates on our status page.

  2. monitoring Jul 29, 2026, 04:06 AM UTC

    Update on the technical issue affecting emails sent from Accelo We want to keep you informed about the ongoing issue. While email delivery has improved, some messages remain queued for processing. We are working closely with our provider to get this fully resolved as soon as possible. We understand the inconvenience and are working hard to restore services quickly. Thank you for your patience.

  3. resolved Jul 29, 2026, 01:30 PM UTC

    The issue affecting emails sent from Accelo has now been fully resolved. Our team worked closely with our email provider to identify and address the root cause, and email delivery has returned to normal. We appreciate your patience while we worked through the issue and apologize for any inconvenience it may have caused.

Read the full incident report →

Notice November 13, 2025 Current Issue with Invoice PDF Generation 2h 8m

Started Nov 13, 2025, 02:58 PM UTC· resolved Nov 13, 2025, 05:07 PM UTC

  1. investigating Nov 13, 2025, 02:58 PM UTC

    We’re currently experiencing an issue affecting PDF generation for non-project-related invoices. While the PDF file will generate, it may appear blank. Our team is treating this with high priority and working on a resolution. In the meantime, if you need to send an invoice to a client and are connected to Xero or QuickBooks, your invoices will still sync with those platforms and can be sent directly from there as a temporary workaround.

  2. investigating Nov 13, 2025, 03:39 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 13, 2025, 03:40 PM UTC

    A fix has been implemented, and we are now seeing invoices and their PDFs being generated correctly. We will continue to monitor to ensure the issue remains resolved.

  4. resolved Nov 13, 2025, 05:07 PM UTC

    This incident has been resolved. All affected invoices have been successfully regenerated, and our Support team will be contacting impacted clients with additional details. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Notice October 20, 2025 Activity Creation and Editor Performance 6h 18m

Started Oct 20, 2025, 05:00 PM UTC· resolved Oct 20, 2025, 11:19 PM UTC

  1. investigating Oct 20, 2025, 05:00 PM UTC

    We are experiencing issues with our cloud service provider on the AWS us-east-1 region, specifically around creating activities, which includes notes, time logs, and emails. All other systems operational.

  2. identified Oct 20, 2025, 05:40 PM UTC

    When trying to create activities users will be met with a "Failed to load editor" message. We are currently experiencing this service disruption due to a widespread AWS (Amazon Web Services) outage impacting multiple systems globally. Our platform relies on AWS infrastructure, and as a result, some services may be unavailable or degraded. We are actively monitoring AWS’s progress and will restore full functionality as soon as their systems are stable. Thank you for your patience and understanding.

  3. identified Oct 20, 2025, 07:41 PM UTC

    The issue with AWS is still unstable and we continue to experience issues with activity creation. We are actively monitoring AWS’s progress and will restore full functionality as soon as their systems are stable. Thank you for your patience and understanding.

  4. identified Oct 20, 2025, 11:12 PM UTC

    We have confirmation that the issue has been resolved. After the resolution was announced by AWS, our team immediately completed thorough testing and can confirm we are no longer seeing any system issues related to the recent AWS outage.

  5. resolved Oct 20, 2025, 11:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 5, 2025 Service Disruption: Global Search and Stream Issue 1d 5h

Started Oct 05, 2025, 09:25 PM UTC· resolved Oct 07, 2025, 02:44 AM UTC

  1. investigating Oct 05, 2025, 09:25 PM UTC

    We want to inform you that we are currently experiencing an issue affecting Global Search and Stream functionality. Out time is actively investigating the problem and working on a resolution. Start Time: Sunday, October 5, 2025 1:20pm MST Impact: Global Search and Stream Functionality Current Status: Under Investigation We understand the inconvenience and are working hard to restore services as soon as possible. Thank you for your patience

  2. monitoring Oct 05, 2025, 09:50 PM UTC

    Update: Sunday, October 5, 2025 @ 3:36pm MST We want to inform you that the issue has been identified and fix is in place. We are currently monitoring the issue. Time: Sunday, October 5, 2025 @ 3:06pm MST Current Status: Monitoring We understand the inconvenience and are working hard to restore service. Thank you for your patience.

  3. investigating Oct 06, 2025, 02:22 PM UTC

    Update: Monday, October 6, 2025 @ 8:20am MST Current Status: Monitoring The underlying issue has been identified and fix is in place. While we continue to monitor the issue, Stream activities may not be 100% visible but a full list can be accessed from the "List & Export" option on the V3 classic stream tab. We understand the inconvenience and are working hard to restore service. Thank you for your patience.

  4. monitoring Oct 06, 2025, 02:24 PM UTC

    Update: Monday, October 6, 2025 @ 8:24am MST Current Status: Monitoring The underlying issue has been identified and fix is in place. While we continue to monitor the issue, Stream activities may not be 100% visible but a full list can be accessed from the "List & Export" option on the V3 classic stream tab. Searching for items may also not display all results. We understand the inconvenience and are working hard to restore service. Thank you for your patience.

  5. resolved Oct 07, 2025, 02:44 AM UTC

    Incident Duration: Sunday, October 5, 2025 1:20pm MST – Sunday, October 5, 2025 3:06pm MST Root Cause: The search reader service experienced a memory issue, which temporarily prevented new data from being indexed into the database. Actions Taken: The affected service was rebooted to restore functionality, and the indexing process has resumed. We're actively monitoring as the system catches up to ensure all data is fully up to date. Preventative Measures: We've reviewed the reader's memory allocation and monitoring thresholds to prevent recurrence. If you experience any lingering search issues, please reach out to our support team. We sincerely appreciate your patience and understanding.

Read the full incident report →

Notice July 25, 2025 20025/07/25 Incident –

Started Jul 25, 2025, 07:00 AM UTC· resolved Jul 25, 2025, 07:00 AM UTC

  1. resolved Jul 25, 2025, 07:00 AM UTC

    On July 25th, Accelo was alerted of an error that was causing issues accessing the system for some of our users. It was reported internally and eventually users began reporting the error. After investigation, it was confirmed that the cause was by Amazon Web Services (AWS) storage system, a defect was confirmed and the database cluster was fully resolved.

Read the full incident report →