down
Is Manus down?
Check Manus availability, incident history, downtime reports, and website performance.
https://manus.im/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for Manus
Last 24 hoursThere is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.
Last collection attempt: 2026-10-20 11:58:53 UTC · Insufficient activity.
No user-submitted outage reports in the last 24 hours.
Manus outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Manus website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-10-22 00:09:51 UTC.
Checked address: https://manus.im/
DNS lookup: 6 ms · TCP connection: 1 ms · TLS handshake: 4 ms. Certificate expires 2027-03-01; trusted connection: yes.
100%
Successful website checks (24h)
136 successful / 136 measurable checks
353 ms
Median response time
560 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Manus official status · fetched 2026-10-21 23:59:00 UTC
3 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| manus.im | operational |
| api.manus.im | operational |
| manus computer | operational |
Official incident timeline
No product-matched incidents are available in the collected provider history. This does not prove that no incident occurred.
Recovery tracker
No recent recovery can be established from available evidence.
6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 347 ms · Earlier median: 354 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Query “is manus” · observed 2026-10-21 23:53:24 UTC · 0 newly observed problem phrases.
Query “manus” · observed 2026-10-21 23:53:24 UTC · 0 newly observed problem phrases.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Manus.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
About Manus status on Iszdown
Check Manus availability, incident history, downtime reports, and website performance.
This page combines the available Manus report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
3 product-matched official components are listed above. Latest public website measurement: 2026-10-22T00:09:51.000Z.
Visit the official Manus website · Official provider status · How it works
What to check when Manus is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Manus will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Manus is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Manus outage history
No product-matched official incidents have been archived for this service in the displayed history. This does not establish that it has never had an outage. See the daily calendar for other available evidence.
Frequently asked questions about Manus
Is Manus down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:13:54.000Z.
How many Manus outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Manus show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Manus feature.
When was Manus status last updated?
The latest status observation was 2026-10-21T23:59:00.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Manus had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Manus or report a problem?
Use “Watch this service” to save Manus in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Manus
Check a related product separately; its status can differ from Manus.