AutoDS Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AutoDS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 27, 2026 | Service DisruptionThe infrastructure issues affecting our platform have now been resolved, and all services are operating normally. Our team has implemented fixes and continues to monitor the system to ensure stability. We sincerely… | 2h 13m | Resolved |
| Apr 27, 2026 | General connectivity issues with eBay integrationThe issue affecting eBay integrations has been resolved. Functionality for importing and editing products has returned to normal. This disruption was caused by a broader eBay outage, which now appears to be stable. We… | 26h 56m | Resolved |
| Apr 14, 2026 | ⚠️ Live Chat Support — Temporary DelaysThis incident has been resolved. | 1h 44m | Resolved |
| Mar 28, 2026 | Issues accessing AutoDS via ShopifyThis incident has been resolved. | 13h 33m | Resolved |
| Mar 14, 2026 | Shopify App currently unavailableThis incident has been resolved. | 2h 20m | Resolved |
| Feb 26, 2026 | Issues with Shopify LoginThis incident has been resolved. | 1h 44m | Resolved |
| Jan 23, 2026 | Service Incident: Shopify App currently unavailableThis incident has been resolved. | 3h 35m | Resolved |
| Jan 9, 2026 | Incident: CRM Service Disruption (Live Chat Widget)This incident has been resolved. | 55 min | Resolved |
| Dec 8, 2025 | Customer support service maintenanceOur migration to the new customer support platform has now been successfully completed. All services are operating normally again, and you should no longer experience delays or disruptions when contacting our support… | 22h 57m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next AutoDS incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This AutoDS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AutoDS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single AutoDS outage in this window ran 1d 2h, against a mean recovery of 8h 26m. If you depend on AutoDS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.