- Detected by Pingoru
- Jun 15, 2026, 03:43 PM UTC
- Resolved
- Jun 15, 2026, 05:04 PM UTC
- Duration
- 1h 21m
Affected: Background Workers
Timeline · 3 updates
-
investigating Jun 15, 2026, 03:43 PM UTC
We’re seeing delays of up to 15 minutes when processing ticket attachments. Our team is investigating the cause.
-
monitoring Jun 15, 2026, 04:23 PM UTC
We’ve made some adjustments and Ticket Attachment performance has improved. We’ll continue to monitor to ensure platform stability.
-
resolved Jun 15, 2026, 05:04 PM UTC
Ticket Attachment upload performance has returned to normal operating parameters. This issue is resolved. We will continue monitoring to ensure system stability.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 06:30 PM UTC
- Resolved
- May 13, 2026, 11:43 PM UTC
- Duration
- 5h 12m
Affected: Background Workers
Timeline · 3 updates
-
investigating May 13, 2026, 06:30 PM UTC
We’re seeing reports that PDF generation isn’t functioning as expected. This affects invoices, reports, and other places where PDFs are utilized. Our team is actively investigating.
-
monitoring May 13, 2026, 06:47 PM UTC
Our team has made adjustments and PDFs are generating as expected. We will continue to monitor to ensure stability.
-
resolved May 13, 2026, 11:43 PM UTC
RepairShopr PDF services are fully operational. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 05:22 PM UTC
- Resolved
- May 01, 2026, 04:55 PM UTC
- Duration
- 1d 23h
Affected: Third Party Services
Timeline · 3 updates
-
investigating Apr 29, 2026, 05:22 PM UTC
We are experiencing an issue with our third party, which sends email notifications from our platform. BYO SMTP, previously-existing Verified Email Domains, and platform emails like notifications, alerts, and account verifications are not impacted. We are working with our third party to resolve this quickly. We appreciate your patience as we work to resolve this issue.
-
monitoring May 01, 2026, 05:35 AM UTC
Outgoing email is functioning as expected. Our team will continue to monitor our email performance to ensure stability. Outgoing emails that were queued to send during the outage will be sent automatically. Please note that verifying your domain and/or enabling SMTP will not only allow your account to continue to send emails during an outage, but also will reduce the chances of your outgoing emails ending up in your clients’ spam folders. Steps to enable these features can be found at the links below. Verify domains: https://repair.uservoice.com/knowledgebase/articles/2015111-verified-email-domains Enable SMTP: https://repair.uservoice.com/knowledgebase/articles/1941568-bring-your-own-smtp
-
resolved May 01, 2026, 04:55 PM UTC
Emails continue to send as expected. This issue is resolved. Please note that verifying your domain or enabling SMTP will not only allow your account to continue to send emails during an outage, but also will reduce the chances of your outgoing emails ending up in your clients’ spam folders. Steps to enable these features can be found at the links below. Verify domains: https://repair.uservoice.com/knowledgebase/articles/2015111-verified-email-domains Enable SMTP: https://repair.uservoice.com/knowledgebase/articles/1941568-bring-your-own-smtp
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 10:38 PM UTC
- Resolved
- Apr 24, 2026, 06:54 PM UTC
- Duration
- 20h 15m
Affected: Application Server
Timeline · 3 updates
-
investigating Apr 23, 2026, 10:38 PM UTC
We are currently investigating reports where Ticket Custom Fields may appear as blank when an existing ticket is opened in the Edit view. Because values are cleared when editing, if a ticket is saved while these fields appear blank, the previous values will be overwritten with blank values. Our engineering team is working to identify the root cause and a resolution. We will provide further updates as more information becomes available.
-
monitoring Apr 24, 2026, 01:58 AM UTC
Ticket Custom Fields are populating on the ticket edit screen as expected. We will continue to monitor to ensure stability.
-
resolved Apr 24, 2026, 06:54 PM UTC
Ticket Custom Fields continue to populate on the ticket edit screen as expected. This issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 12:03 AM UTC
- Resolved
- Mar 27, 2026, 03:41 PM UTC
- Duration
- 1d 15h
Affected: Third Party Services
Timeline · 4 updates
-
investigating Mar 26, 2026, 12:03 AM UTC
We are currently investigating reports of issues impacting invoice syncing with QuickBooks. This includes delays or errors affecting both newly created invoices, recurring invoices, and payment syncs that were created after March 25th, 2026. Our team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will provide updates as more information becomes available.
-
investigating Mar 26, 2026, 01:44 AM UTC
We have identified that the issue is related to the use of custom tax rate settings. As we continue working toward a full resolution, a temporary workaround is available: assigning a 0% tax rate to the RepairShopr invoice will allow invoices to sync properly with QuickBooks. You may need to create a 0% tax rate in RepairShopr if one does not already exist. After the invoice has synced over, you will be able to manually change the tax rate within QuickBooks directly to reflect the proper amount. Our team is actively investigating a permanent fix and will share further updates as they become available.
-
monitoring Mar 26, 2026, 04:08 PM UTC
Invoices with custom sales tax rates are successfully syncing to QuickBooks Online. We are actively monitoring QBO invoice syncing behavior to ensure stability. We are also investigating the root cause of the business validation errors to prevent them in the future. We will provide additional updates as they become available.
-
resolved Mar 27, 2026, 03:41 PM UTC
Invoices with and without custom sales tax rates are syncing successfully to QuickBooks Online. Our team will continue monitoring to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 06:52 PM UTC
- Resolved
- Mar 16, 2026, 05:02 PM UTC
- Duration
- 12d 22h
Affected: Third Party Services
Timeline · 4 updates
-
identified Mar 03, 2026, 06:52 PM UTC
We are experiencing an issue with our third party, which sends SMS notifications from our platform. BYO Twilio and Flowroute accounts are not affected. We are working with our third party to resolve this quickly. We appreciate your patience as we work to resolve this issue.
-
identified Mar 09, 2026, 09:12 PM UTC
We are continuing to work closely with our third-party provider to restore SMS functionality. Our team is monitoring the situation and we will provide another update once more information becomes available.
-
identified Mar 13, 2026, 08:02 PM UTC
We are still working closely with our third-party provider to restore SMS functionality. Our team is monitoring the situation and we will provide another update once more information becomes available.
-
resolved Mar 16, 2026, 05:02 PM UTC
Outbound SMS messaging for RepairShopr accounts has been fully restored.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 05:08 PM UTC
- Resolved
- Feb 04, 2026, 07:30 PM UTC
- Duration
- 2h 22m
Affected: Application Server
Timeline · 2 updates
-
investigating Feb 04, 2026, 05:08 PM UTC
The ‘Internal Server Error’ message affects the invoice UI when updating the Invoice Details fields such as Invoice Name, Invoice Template, Due Date, PO, etc. The updates will reflect upon refreshing the page. Our team is actively working on correcting this issue and will be sure to post updates with our progress.
-
resolved Feb 04, 2026, 07:30 PM UTC
We have deployed an update, and updates to the Invoice Details section (such as Invoice Name, Due Date, PO, etc.) are registering as expected with no errors. This issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 08:19 PM UTC
- Resolved
- Jan 09, 2026, 08:58 PM UTC
- Duration
- 38m
Affected: Third Party Services
Timeline · 2 updates
-
identified Jan 09, 2026, 08:19 PM UTC
The third party service we use for support communication is currently experiencing an outage. Phone calls, chats, and emails to RepairShopr Support will either be unavailable or have delayed response until the outage is resolved by our third party. We will post updates here as we receive them.
-
resolved Jan 09, 2026, 08:58 PM UTC
We have confirmed that our third-party service provider has resolved the underlying issue. As a result, all RepairShopr support channels, including phone, chat, and email, are now fully operational. We appreciate your patience while we worked to restore these services.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 01:39 PM UTC
- Resolved
- Dec 19, 2025, 05:03 PM UTC
- Duration
- 1d 3h
Affected: Background Workers
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 11:53 AM UTC
- Resolved
- Nov 18, 2025, 07:58 PM UTC
- Duration
- 8h 4m
Affected: Application Server
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 06:22 PM UTC
- Resolved
- Nov 14, 2025, 08:15 PM UTC
- Duration
- 1h 53m
Affected: Third Party Services
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2025, 07:47 PM UTC
- Resolved
- Oct 30, 2025, 04:32 PM UTC
- Duration
- 1d 20h
Affected: Application Server
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 06:11 PM UTC
- Resolved
- Oct 21, 2025, 09:24 PM UTC
- Duration
- 1d 3h
Affected: Background Workers
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 06:02 PM UTC
- Resolved
- Sep 24, 2025, 04:28 PM UTC
- Duration
- 1d 22h
Affected: Background Workers
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 06:23 AM UTC
- Resolved
- Sep 15, 2025, 03:46 PM UTC
- Duration
- 7d 9h
Affected: Third Party Services
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 07:53 PM UTC
- Resolved
- Aug 12, 2025, 03:36 PM UTC
- Duration
- 5d 19h
Affected: Third Party Services
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 01:55 PM UTC
- Resolved
- Aug 08, 2025, 06:52 PM UTC
- Duration
- 3d 4h
Affected: Third Party Services
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2025, 01:00 PM UTC
- Resolved
- Jun 26, 2025, 09:00 PM UTC
- Duration
- 8h
Affected: Background Workers
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 01:29 PM UTC
- Resolved
- Jun 25, 2025, 06:55 PM UTC
- Duration
- 2d 5h
Affected: Third Party Services
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 09:42 PM UTC
- Resolved
- Jul 07, 2025, 09:43 PM UTC
- Duration
- 17d
Affected: Third Party Services
Read the full incident report →