Gurobi Optimization Outage History
Gurobi Optimization is up right nowPingoru has recorded 50 incidents for Gurobi Optimization: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 524 (0%) |
Incidents, newest first
Major June 12, 2026 Gurobi Instant Cloud Partial Outage 27m Gurobi AWS us-east-1, Gurobi AWS us-west-1, Gurobi AWS eu-central-1, Instant Cloud Provisioning - Global and 1 more
Started Jun 12, 2026, 09:10 PM UTC· resolved Jun 12, 2026, 09:37 PM UTC
- investigating Jun 12, 2026, 09:10 PM UTC
We are currently investigating an issue affecting machine startup in Gurobi Instant Cloud. Our team is working to resolve the issue and determine full scope. We will provide an update as soon as possible.
- resolved Jun 12, 2026, 09:37 PM UTC
Our services experienced temporary failures and have since been restarted. Gurobi Instant Cloud should now be available for normal use. We are continuing to monitor the situation. Please contact us if you experience any further issues.
- postmortem Jun 15, 2026, 06:04 PM UTC
Following 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 fresh containers of our micro-services solved the issue. We sincerely apologize for any inconvenience this may have caused, and we have since reviewed and improved our scaling policies to prevent this type of issue from occurring again.
Notice February 6, 2026 Web Services DNS issue 24m Gurobi Website, Gurobi User Portal, Web License Service - Global
Started Feb 06, 2026, 11:51 PM UTC· resolved Feb 07, 2026, 12:16 AM UTC
- investigating Feb 06, 2026, 11:51 PM UTC
We are currently experiencing an issue affecting access to some Gurobi services. Users may see DNS resolution failures, resulting in intermittent or complete inability to connect to gurobi.com, portal.gurobi.com, and licensing endpoints. We are working to resolve the issue.
- resolved Feb 07, 2026, 12:16 AM UTC
The 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 responses again, and services are operating normally. A subset of users may continue to see issues if their local DNS resolvers maintain stale cache entries, but these will clear automatically. Thank you for your patience while we investigated and resolved the issue.
Major October 20, 2025 AWS Operational Issue US-EAST-1 (N. Virginia) 9h 19m Gurobi AWS us-east-1, Gurobi User Portal, Instant Cloud Provisioning - Global, Web License Service - Global
Started Oct 20, 2025, 12:56 PM UTC· resolved Oct 20, 2025, 10:16 PM UTC
- investigating Oct 20, 2025, 12:56 PM UTC
We are currently experiencing connectivity issues with our services hosted in AWS region US-EASt-1. AWS has acknowledged a service disruption in these region and is actively working to resolve the issue. To minimize impact, we recommend customers temporarily switch to an alternative AWS region until full service is restored. You can monitor the latest updates directly from AWS at AWS Service Health Dashboard.
- investigating Oct 20, 2025, 12:58 PM UTC
We are continuing to investigate this issue.
- investigating Oct 20, 2025, 02:55 PM UTC
We are currently experiencing connectivity issues with our services hosted in AWS region US-EAST-1. AWS has acknowledged a service disruption in these region and is actively working to resolve the issue. To minimize impact, we recommend customers temporarily switch to an alternative AWS region until full service is restored. You can monitor the latest updates directly from AWS at AWS Service Health Dashboard.
- resolved Oct 20, 2025, 10:16 PM UTC
This incident has been resolved.