Last checked: 31 seconds ago
Get notified about any outages, downtime or incidents for Gurobi Optimization and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Gurobi Optimization.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Gurobi Cloud Billing | Active |
Gurobi User Portal | Active |
Gurobi Website | Active |
Instant Cloud Manager - Global | Active |
Instant Cloud Provisioning - Global | Active |
Web License Service - Global | Active |
Regions | Active |
Gurobi AWS ap-northeast-1 | Active |
Gurobi AWS ap-southeast-2 | Active |
Gurobi AWS eu-central-1 | Active |
Gurobi AWS us-east-1 | Active |
Gurobi AWS us-west-1 | Active |
Gurobi Azure eastus | Active |
Gurobi Azure westeurope | Active |
Gurobi Azure westus2 | Active |
View the latest incidents for Gurobi Optimization and check for official updates:
Description: The AWS Europe region was impacted by internal networking issues. The issue has been resolved and systems are stable again.
Status: Resolved
Impact: None | Started At: June 15, 2020, 3:04 p.m.
Description: While doing some routine upgrades to the billing system, it was inadvertently taken offline for about 15 minutes. Existing cloud sessions were not affected, but it affected the ability to launch new cloud sessions. All systems are fully functioning again.
Status: Resolved
Impact: Major | Started At: Jan. 11, 2020, 1:30 a.m.
Description: About 14:20 UTC on 2019-12-04, the Gurobi account and cloud billing system stopped responding. Gurobi IT staff were alerted immediately, who contacted Amazon Web Services \(AWS\) for emergency assistance. The root cause was slow EFS \(NFS\) performance, which caused the web server to timeout. We restored service by temporarily switching to a local backup filesystem. Gurobi Cloud is designed with redundancy throughout, and it’s ironic that this outage was caused by a performance issue with a fault-tolerant system. We have opened a second support case with AWS to fix the file system performance and restore redundant servers. We apologize for any inconvenience and thank you for your business.
Status: Postmortem
Impact: Major | Started At: Dec. 4, 2019, 3:20 p.m.
Description: All systems should be functioning normally again
Status: Resolved
Impact: Minor | Started At: Oct. 17, 2019, 9:16 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.