SugarSync Outage History
17 incidents recorded over the last 365 days, 7 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 SugarSync Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 8, 2026 | Login / Access DegradationThank you for your patience. Performance has now stabilized across the system. Our engineers will continue to monitor. | 54h 43m | Resolved |
| Aug 26, 2026 | Support limited due to network maintenanceThis incident has been resolved. Support is fully operational. | 1h 2m | Resolved |
| Aug 26, 2026 | Support Limited Due to Internal MaintenanceOur support team currently experiencing limited access to internal tools due to network maintenance. SugarSync accounts and data are unaffected; customers can log in and use the service as normal. Our team is actively… | 6 min | Resolved |
| Aug 5, 2026 | Network Infrastructure MaintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Apr 15, 2026 | Login and connectivity issuesOur engineers have fully resolved the issue affecting connectivity and access to SugarSync. | 21h 6m | Resolved |
| Apr 12, 2026 | Login and connectivity issuesOur engineers have resolved the issue affecting connectivity and access to SugarSync. All systems are functioning. | 37h 53m | Resolved |
| Apr 9, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 8, 2026 | Email Message DelaysGoogle has indicated that the issue has been resolved. | 4h 34m | Resolved |
| Mar 30, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 26, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 25, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 18, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 17, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 16, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 12, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 9, 2026 | Network MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 18, 2025 | Services affected due to Cloudflare outageThis incident has been resolved. | 6h 45m | 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 SugarSync 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 SugarSync 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 SugarSync 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 SugarSync outage in this window ran 2d 6h, against a mean recovery of 8h 36m. If you depend on SugarSync 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.