Lotame Ops Outage History
27 incidents recorded over the last 365 days, 3 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 Lotame Ops Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 3, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Oct 20, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Oct 19, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 15, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 14, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 25, 2026 | Platform UI/API DegradationThere were briefly platform login issues between 10:15 and 10:45AM EDT. This issue has been resolved. | -39 min | Resolved |
| Aug 13, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 12, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 5, 2026 | Dropbox OutageDropbox was briefly unavailable between 8:15 and 8:45AM. The issue was resolved and client access was confirmed. | -53544 min | Resolved |
| Jul 23, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jul 13, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 22, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 11, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 1, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 18, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 30, 2026 | Edge Services MigrationThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 27, 2026 | Edge Services MigrationThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 22, 2026 | Edge Services DegredationThis incident has been resolved. | 2h 2m | Resolved |
| Apr 20, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 15, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 26, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 29, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 28, 2026 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 14, 2026 | UI/API MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 6, 2026 | Edge Services MigrationThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 10, 2025 | Dropbox MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Lotame Ops 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 Lotame Ops 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 Lotame Ops 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 Lotame Ops outage in this window ran 3h, against a mean recovery of 1h 7m. If you depend on Lotame Ops 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.