Pix4D Outage History
8 incidents recorded over the last 365 days, 5 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 Pix4D Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 21, 2026 | Elevated API ErrorsAll cloud services are fully operational and stable. We apologize for the inconvenience caused by the outage. | 54h 26m | Resolved |
| Feb 28, 2026 | Decommissioning Notice: Pix4Dmapper cloud pipelineThe scheduled maintenance has been completed. | 1 min | Scheduled |
| Feb 11, 2026 | Cloud UI - annotations unexpectedly deletedWe have restored the annotations that were deleted during the time of the incident. We recommend refreshing the affected datasets. | 52h 5m | Resolved |
| Jan 22, 2026 | Cloud API and site downAll services are restored correctly with the revert of the change. We do not notice any further problem. Sorry for the inconvenience caused by the API outage. | 23 min | Resolved |
| Dec 7, 2025 | Databases upgradeThe maintenance is completed. | 2h 0m | Scheduled |
| Nov 25, 2025 | API Infrastructure UpgradeThe maintenance is finished. We will keep observing the traffic all day and perform adjustment when needed. | 2h 0m | Scheduled |
| Nov 10, 2025 | High database loadWe are closing the incident as resolved. | 2h 47m | Resolved |
| Nov 7, 2025 | High database loadThe load is resolved now. The incident is closed now. | 2h 18m | 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 Pix4D 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 Pix4D 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 Pix4D 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 Pix4D outage in this window ran 2d 6h, against a mean recovery of 14h 30m. If you depend on Pix4D 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.