User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 50 min ago. Last stored result reached it in 3185 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:00 | 0 | 0.0 | 889 ms | 0 |
| 11:00 | 0 | 0.0 | 1894 ms | 0 |
| 13:15 | 0 | 0.0 | 3355 ms | 0 |
| 15:15 | 0 | 0.0 | 1632 ms | 0 |
| 17:15 | 0 | 0.0 | 2303 ms | 0 |
| 19:30 | 0 | 0.0 | 435 ms | 0 |
| 20:30 | 0 | 0.0 | 2744 ms | 0 |
| 22:30 | 0 | 0.0 | 2446 ms | 0 |
| 00:30 | 0 | 0.0 | 489 ms | 0 |
| 02:45 | 0 | 0.0 | 337 ms | 0 |
| 04:45 | 0 | 0.0 | 553 ms | 0 |
| 06:45 | 0 | 0.0 | 3185 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Maxim 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 Maxim goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Maxim alerts to Slack, Discord or a webhook — free.
We track Maxim (getmaxim.ai) as part of the AI group. The fastest open-source AI gateway for LLMs, MCP and agents: 50x faster than LiteLLM, with routing, governance, guardrails and observability built in.
Maxim publishes an official status page at status.getmaxim.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1595 ms average, 337–3355 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 Maxim incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1595 ms on average over the last 24 hours (337–3355 ms).
Yes, at https://status.getmaxim.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Maxim here at once, the problem is on Maxim'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 Maxim. 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.