Is Gurobi Optimization down?

Last checked 9m ago
Current status
Gurobi Optimization is up

No incidents right now.

Official status page: https://status.gurobi.com · Polled every 5 minutes · 14 components tracked

Gurobi Optimization is operational right now. Last checked 9m ago; the most recent incident resolved 47d ago.

Real-time Gurobi Optimization status, recent outages, and incident history — pulled directly from Gurobi Optimization's official status page at https://status.gurobi.com every 5 minutes. Pingoru tracks 14 Gurobi Optimization services and has captured 3 incidents in the last 90 days (99.40% uptime). Get email, Slack, Discord, or webhook alerts the moment Gurobi Optimization reports a new incident — free for 5 monitors, no credit card.

Users who monitor Gurobi Optimization also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Gurobi Optimization uptime 99.40% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 27m
    Started Jun 12, 2026, 09:10 PM UTC · Resolved Jun 12, 2026, 09:37 PM UTC
    Gurobi AWS us-east-1Gurobi AWS us-west-1Gurobi AWS eu-central-1Instant Cloud Provisioning - GlobalWeb License Service - Global
    Timeline · 3 updates
    • 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.

    Latest: 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 t…

Outage history

Past 90 days · 1 incident View full outage history →