Gurobi Outage History
9 incidents recorded over the last 365 days, 2 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 Gurobi Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 24, 2026 | Gurobi Cloud Services Upgrade to v13.0.3The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jun 12, 2026 | Gurobi Instant Cloud Partial OutageFollowing a scale down event on our cloud services clusters, some machines were terminated. The containers that were running on these machines did not restart properly, causing a temporary service disruption. Deploying… | 27 min | Resolved |
| May 11, 2026 | Gurobi Cloud Services MaintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| May 4, 2026 | Gurobi Cloud Services Upgrade to v13.0.2The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 6, 2026 | New website!The website migration has been successfully completed and all services are confirmed fully operational. Thank you for your patience during this process and we hope you enjoy the new look! | 1h 0m | Scheduled |
| Feb 23, 2026 | Gurobi Cloud Services MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Feb 6, 2026 | Web Services DNS issueThe DNS resolution issues affecting gurobi.com, portal.gurobi.com, and the license servers have now been fully resolved. All major public DNS resolvers (Google, Cloudflare, AWS, ISP resolvers) are returning valid… | 24 min | Resolved |
| Jan 20, 2026 | Gurobi Cloud Services Upgrade to v13.0.1The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 10, 2025 | Gurobi Cloud Services Upgrade to v13.0.0The 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 Gurobi 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 Gurobi 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 Gurobi 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 Gurobi outage in this window ran 8h, against a mean recovery of 2h 19m. If you depend on Gurobi 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.