Robly Outage History
10 incidents recorded over the last 365 days, 4 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 Robly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 16, 2026 | Robly Systems UpgradeThe scheduled upgrade has been completed and mailing has resumed. | 2h 0m | Scheduled |
| Oct 1, 2026 | Live Chat Support UnavailableThis incident has been resolved. | 26h 59m | Resolved |
| Jun 25, 2026 | General System MaintenanceThe scheduled maintenance has been completed and all queued campaigns have resumed sending. | 6h 0m | Scheduled |
| Apr 17, 2026 | Delayed Email DeliveriesAll services have returned to expected performance levels. Thank you for your patience. | 5h 58m | Resolved |
| Apr 1, 2026 | Robly Database UpdateRobly’s scheduled update has been successfully completed. All systems are now fully operational, and any queued emails have been processed and sent. Thank you for your patience. | 1h 0m | Scheduled |
| Mar 26, 2026 | General System MaintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Mar 5, 2026 | Scheduled Maintenance | 8:30 PM ESTThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 9, 2026 | Third Party In-App Messaging IssueOur third party partner has identified and resolved the issue. All systems are back to operational. | 20 min | Resolved |
| Dec 26, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 8, 2025 | Service InterruptionThis incident has been resolved. | 43h 46m | 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 Robly 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 Robly 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 Robly 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 Robly outage in this window ran 1d 19h, against a mean recovery of 8h 57m. If you depend on Robly 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.