NavVis Outage History
8 incidents recorded over the last 365 days, 6 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 NavVis Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | Security Update: PHP2Shell Vulnerabilities (CVE-2026-109618 and CVE-2026-109619)This incident has been resolved. | 121h 51m | Resolved |
| Jul 2, 2026 | Point cloud exports from Crop & Download uses Site Coordinate System instead of the selected Spatial Reference SystemHello IVION Users, We are pleased to inform you that the issue affecting Crop & Download has been successfully resolved. Our team has implemented a solution, and services are now operating as expected. All point cloud… | 26h 33m | Resolved |
| Apr 23, 2026 | Third party e57 embedded panoramas having wrong orientation after uploadThis incident has been resolved. | 23h 57m | Resolved |
| Apr 23, 2026 | 2D map generationOur developers have identified the root cause of the issue that was causing 2D map generation to get stuck at the "Calculating 2D Map" stage and are preparing fixes to our infrastructure to prevent this from occurring… | 24h 26m | Resolved |
| Mar 13, 2026 | System Software Update Access Temporarily UnavailableThis incident has been resolved. VLX/MLX should be able to get updates given a valid license. | 6h 14m | Resolved |
| Mar 9, 2026 | EU Region InfrastructureThe scheduled maintenance has been completed. | 2h 30m | Scheduled |
| Feb 11, 2026 | Temporary API unavailabilityThis incident has been resolved. All the Core instances that should have the access to the API now do. | 30h 29m | Resolved |
| Jan 19, 2026 | Scheduled Maintenance NoticeDear IVION users, The planned maintenance on your IVION instance has been successfully completed. Your instance is now fully available, and all services are operating normally. No action is required on your side. If… | 3650h 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 NavVis 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 NavVis 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 NavVis 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 NavVis outage in this window ran 152d 2h, against a mean recovery of 20d 5h. If you depend on NavVis 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.