User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
gurobi.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 9 min ago. Last stored result reached it in 280 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 277 ms | 0 |
| Tue 11 | 0 | 0.0 | 325 ms | 0 |
| Tue 14 | 0 | 0.0 | 239 ms | 0 |
| Tue 16 | 0 | 0.0 | 315 ms | 0 |
| Tue 18 | 0 | 0.0 | 294 ms | 0 |
| Tue 20 | 0 | 0.0 | 343 ms | 0 |
| Tue 23 | 0 | 0.0 | 332 ms | 0 |
| Wed 01 | 0 | 0.0 | 360 ms | 0 |
| Wed 03 | 0 | 0.0 | 245 ms | 0 |
| Wed 05 | 0 | 0.0 | 343 ms | 0 |
| Wed 08 | 0 | 0.0 | 302 ms | 0 |
| Wed 10 | 0 | 0.0 | 340 ms | 0 |
| Wed 12 | 0 | 0.0 | 378 ms | 0 |
| Wed 14 | 0 | 0.0 | 339 ms | 0 |
| Wed 16 | 0 | 0.0 | 333 ms | 0 |
| Wed 18 | 0 | 0.0 | 254 ms | 0 |
| Wed 21 | 0 | 0.0 | 329 ms | 0 |
| Wed 23 | 0 | 0.0 | 318 ms | 0 |
| Thu 01 | 0 | 0.0 | 340 ms | 0 |
| Thu 03 | 0 | 0.0 | 305 ms | 0 |
| Thu 05 | 0 | 0.0 | 369 ms | 0 |
| Thu 07 | 0 | 0.0 | 332 ms | 0 |
| Thu 09 | 0 | 0.0 | 336 ms | 0 |
| Thu 11 | 0 | 0.0 | 232 ms | 0 |
| Thu 13 | 0 | 0.0 | 250 ms | 0 |
| Thu 15 | 0 | 0.0 | 323 ms | 0 |
| Thu 17 | 0 | 0.0 | 223 ms | 0 |
| Thu 20 | 0 | 0.0 | 315 ms | 0 |
| Thu 22 | 0 | 0.0 | 299 ms | 0 |
| Fri 00 | 0 | 0.0 | 247 ms | 0 |
| Fri 02 | 0 | 0.0 | 330 ms | 0 |
| Fri 04 | 0 | 0.0 | 406 ms | 0 |
| Fri 06 | 0 | 0.0 | 246 ms | 0 |
| Fri 08 | 0 | 0.0 | 331 ms | 0 |
| Fri 10 | 0 | 0.0 | 335 ms | 0 |
| Fri 12 | 0 | 0.0 | 310 ms | 0 |
| Fri 14 | 0 | 0.0 | 297 ms | 0 |
| Fri 15 | 0 | 0.0 | 333 ms | 0 |
| Fri 17 | 0 | 0.0 | 339 ms | 0 |
| Fri 19 | 0 | 0.0 | 352 ms | 0 |
| Fri 20 | 0 | 0.0 | 343 ms | 0 |
| Fri 22 | 0 | 0.0 | 281 ms | 0 |
| Sat 00 | 0 | 0.0 | 344 ms | 0 |
| Sat 02 | 0 | 0.0 | 232 ms | 0 |
| Sat 04 | 0 | 0.0 | 260 ms | 0 |
| Sat 06 | 0 | 0.0 | 303 ms | 0 |
| Sat 08 | 0 | 0.0 | 280 ms | 0 |
| Sat 10 | 0 | 0.0 | 258 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Gurobi yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Gurobi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gurobi alerts to Slack, Discord or a webhook — free.
Gurobi is listed in our Cloud & developer category and checked at gurobi.com. See how Gurobi turns your toughest business decisions into a single, optimal action plan — built by PhD mathematicians for the world's most complex problems.
Gurobi publishes an official status page at status.gurobi.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 305 ms average, 232–352 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Gurobi incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
305 ms on average over the last 24 hours (232–352 ms).
Yes, at https://status.gurobi.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Gurobi here at once, the problem is on Gurobi's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Gurobi. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.