User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Maxim down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → getmaxim.ai—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 2203 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 2927 ms | 0 |
| Tue 20 | 0 | 0.0 | 1635 ms | 0 |
| Tue 22 | 0 | 0.0 | 296 ms | 0 |
| Wed 00 | 0 | 0.0 | 1225 ms | 0 |
| Wed 02 | 0 | 0.0 | 248 ms | 0 |
| Wed 04 | 0 | 0.0 | 1608 ms | 0 |
| Wed 07 | 0 | 0.0 | 519 ms | 0 |
| Wed 09 | 0 | 0.0 | 1668 ms | 0 |
| Wed 11 | 0 | 0.0 | 1711 ms | 0 |
| Wed 13 | 0 | 0.0 | 3154 ms | 0 |
| Wed 15 | 0 | 0.0 | 4288 ms | 0 |
| Wed 17 | 0 | 0.0 | 3741 ms | 0 |
| Wed 20 | 0 | 0.0 | 391 ms | 0 |
| Wed 22 | 0 | 0.0 | 533 ms | 0 |
| Thu 00 | 0 | 0.0 | 2856 ms | 0 |
| Thu 02 | 0 | 0.0 | 4300 ms | 0 |
| Thu 03 | 0 | 0.0 | 2918 ms | 0 |
| Thu 05 | 0 | 0.0 | 1239 ms | 0 |
| Thu 07 | 0 | 0.0 | 1308 ms | 0 |
| Thu 09 | 0 | 0.0 | 889 ms | 0 |
| Thu 11 | 0 | 0.0 | 1894 ms | 0 |
| Thu 13 | 0 | 0.0 | 3355 ms | 0 |
| Thu 15 | 0 | 0.0 | 1632 ms | 0 |
| Thu 17 | 0 | 0.0 | 2303 ms | 0 |
| Thu 19 | 0 | 0.0 | 435 ms | 0 |
| Thu 20 | 0 | 0.0 | 2744 ms | 0 |
| Thu 22 | 0 | 0.0 | 2446 ms | 0 |
| Fri 00 | 0 | 0.0 | 489 ms | 0 |
| Fri 02 | 0 | 0.0 | 337 ms | 0 |
| Fri 04 | 0 | 0.0 | 553 ms | 0 |
| Fri 06 | 0 | 0.0 | 3185 ms | 0 |
| Fri 09 | 0 | 0.0 | 1197 ms | 0 |
| Fri 11 | 0 | 0.0 | 1735 ms | 0 |
| Fri 13 | 0 | 0.0 | 2018 ms | 0 |
| Fri 15 | 0 | 0.0 | 2586 ms | 0 |
| Fri 17 | 0 | 0.0 | 2037 ms | 0 |
| Fri 18 | 0 | 0.0 | 307 ms | 0 |
| Fri 20 | 0 | 0.0 | 2284 ms | 0 |
| Fri 22 | 0 | 0.0 | 1827 ms | 0 |
| Sat 00 | 0 | 0.0 | 1452 ms | 0 |
| Sat 02 | 0 | 0.0 | 360 ms | 0 |
| Sat 04 | 0 | 0.0 | 402 ms | 0 |
| Sat 06 | 0 | 0.0 | 1022 ms | 0 |
| Sat 08 | 0 | 0.0 | 2220 ms | 0 |
| Sat 10 | 0 | 0.0 | 286 ms | 0 |
| Sat 13 | 0 | 0.0 | 443 ms | 0 |
| Sat 15 | 0 | 0.0 | 308 ms | 0 |
| Sat 18 | 0 | 0.0 | 2203 ms | 0 |
Reliability
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Maxim badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Maxim yet. Outages of 10 minutes or more get their own page here.
Having trouble with Maxim?
One report per service every 10 minutes from this network. No account.
Follow Maxim
Get an email when Maxim goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
About Maxim
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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 994 ms average, 253–2284 ms range across 15 successful checks.
Questions
Is Maxim down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Maxim last down?
We have not recorded a public Maxim incident since monitoring began 8 days ago.
What is Maxim's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Maxim respond?
994 ms on average over the last 24 hours (253–2284 ms).
Does Maxim have an official status page?
Yes, at https://status.getmaxim.ai.
Maxim not working for me but the status is fine. What now?
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.