User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
partly.com · AI
Is Partly 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 → partly.com—
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 299 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 361 ms | 0 |
| Mon 18 | 0 | 0.0 | 439 ms | 0 |
| Mon 20 | 0 | 0.0 | 374 ms | 0 |
| Mon 22 | 0 | 0.0 | 309 ms | 0 |
| Tue 00 | 0 | 0.0 | 281 ms | 0 |
| Tue 02 | 0 | 0.0 | 394 ms | 0 |
| Tue 04 | 0 | 0.0 | 444 ms | 0 |
| Tue 06 | 0 | 0.0 | 296 ms | 0 |
| Tue 09 | 0 | 0.0 | 269 ms | 0 |
| Tue 11 | 0 | 0.0 | 288 ms | 0 |
| Tue 13 | 0 | 0.0 | 335 ms | 0 |
| Tue 15 | 0 | 0.0 | 953 ms | 0 |
| Tue 17 | 0 | 0.0 | 966 ms | 0 |
| Tue 20 | 0 | 0.0 | 379 ms | 0 |
| Tue 22 | 0 | 0.0 | 343 ms | 0 |
| Wed 00 | 0 | 0.0 | 279 ms | 0 |
| Wed 02 | 0 | 0.0 | 386 ms | 0 |
| Wed 05 | 0 | 0.0 | 267 ms | 0 |
| Wed 07 | 0 | 0.0 | 450 ms | 0 |
| Wed 09 | 0 | 0.0 | 299 ms | 0 |
| Wed 11 | 0 | 0.0 | 329 ms | 0 |
| Wed 13 | 0 | 0.0 | 355 ms | 0 |
| Wed 16 | 0 | 0.0 | 400 ms | 0 |
| Wed 18 | 0 | 0.0 | 334 ms | 0 |
| Wed 20 | 0 | 0.0 | 373 ms | 0 |
| Wed 22 | 0 | 0.0 | 792 ms | 0 |
| Thu 00 | 0 | 0.0 | 288 ms | 0 |
| Thu 02 | 0 | 0.0 | 339 ms | 0 |
| Thu 04 | 0 | 0.0 | 293 ms | 0 |
| Thu 06 | 0 | 0.0 | 900 ms | 0 |
| Thu 09 | 0 | 0.0 | 359 ms | 0 |
| Thu 11 | 0 | 0.0 | 451 ms | 0 |
| Thu 13 | 0 | 0.0 | 315 ms | 0 |
| Thu 15 | 0 | 0.0 | 260 ms | 0 |
| Thu 17 | 0 | 0.0 | 995 ms | 0 |
| Thu 19 | 0 | 0.0 | 218 ms | 0 |
| Thu 21 | 0 | 0.0 | 288 ms | 0 |
| Thu 23 | 0 | 0.0 | 419 ms | 0 |
| Fri 01 | 0 | 0.0 | 294 ms | 0 |
| Fri 03 | 0 | 0.0 | 396 ms | 0 |
| Fri 05 | 0 | 0.0 | 283 ms | 0 |
| Fri 07 | 0 | 0.0 | 275 ms | 0 |
| Fri 09 | 0 | 0.0 | 304 ms | 0 |
| Fri 10 | 0 | 0.0 | 268 ms | 0 |
| Fri 12 | 0 | 0.0 | 214 ms | 0 |
| Fri 14 | 0 | 0.0 | 218 ms | 0 |
| Fri 16 | 0 | 0.0 | 442 ms | 0 |
| Fri 18 | 0 | 0.0 | 299 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Partly 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 Partly yet. Outages of 10 minutes or more get their own page here.
Having trouble with Partly?
One report per service every 10 minutes from this network. No account.
Follow Partly
Get an email when Partly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Partly alerts to Slack, Discord or a webhook — free.
About Partly
Partly, at partly.com, is one of the AI services we monitor. Partly builds frontier AI for repair: Interpreter, the AI model that understands repair, powering Partly Repair AI and Partly Labs for repair businesses.
Partly publishes an official status page at status.partly.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 308 ms average, 214–442 ms range across 12 successful checks.
Questions
Is Partly down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Partly last down?
We have not recorded a public Partly incident since monitoring began 7 days ago.
What is Partly's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Partly respond?
308 ms on average over the last 24 hours (214–442 ms).
Does Partly have an official status page?
Yes, at https://status.partly.com.
Partly 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 Partly here at once, the problem is on Partly'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 Partly. 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.