User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
replicated.com · Cloud & developer
Is Replicated 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 → replicated.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 30 min ago. Last stored result reached it in 37 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 13 | 0 | 0.0 | 36 ms | 0 |
| Mon 15 | 0 | 0.0 | 75 ms | 0 |
| Mon 17 | 0 | 0.0 | 60 ms | 0 |
| Mon 19 | 0 | 0.0 | 112 ms | 0 |
| Mon 21 | 0 | 0.0 | 230 ms | 0 |
| Mon 23 | 0 | 0.0 | 64 ms | 0 |
| Tue 01 | 0 | 0.0 | 85 ms | 0 |
| Tue 04 | 0 | 0.0 | 48 ms | 0 |
| Tue 06 | 0 | 0.0 | 96 ms | 0 |
| Tue 08 | 0 | 0.0 | 45 ms | 0 |
| Tue 10 | 0 | 0.0 | 42 ms | 0 |
| Tue 12 | 0 | 0.0 | 74 ms | 0 |
| Tue 14 | 0 | 0.0 | 57 ms | 0 |
| Tue 17 | 0 | 0.0 | 55 ms | 0 |
| Tue 19 | 0 | 0.0 | 40 ms | 0 |
| Tue 21 | 0 | 0.0 | 39 ms | 0 |
| Tue 23 | 0 | 0.0 | 99 ms | 0 |
| Wed 01 | 0 | 0.0 | 38 ms | 0 |
| Wed 04 | 0 | 0.0 | 77 ms | 0 |
| Wed 06 | 0 | 0.0 | 36 ms | 0 |
| Wed 08 | 0 | 0.0 | 63 ms | 0 |
| Wed 11 | 0 | 0.0 | 122 ms | 0 |
| Wed 13 | 0 | 0.0 | 122 ms | 0 |
| Wed 15 | 0 | 0.0 | 57 ms | 0 |
| Wed 17 | 0 | 0.0 | 66 ms | 0 |
| Wed 19 | 0 | 0.0 | 106 ms | 0 |
| Wed 21 | 0 | 0.0 | 92 ms | 0 |
| Wed 23 | 0 | 0.0 | 80 ms | 0 |
| Thu 02 | 0 | 0.0 | 79 ms | 0 |
| Thu 04 | 0 | 0.0 | 91 ms | 0 |
| Thu 06 | 0 | 0.0 | 159 ms | 0 |
| Thu 08 | 0 | 0.0 | 134 ms | 0 |
| Thu 10 | 0 | 0.0 | 66 ms | 0 |
| Thu 12 | 0 | 0.0 | 74 ms | 0 |
| Thu 14 | 0 | 0.0 | 40 ms | 0 |
| Thu 16 | 0 | 0.0 | 37 ms | 0 |
| Thu 18 | 0 | 0.0 | 76 ms | 0 |
| Thu 20 | 0 | 0.0 | 120 ms | 0 |
| Thu 22 | 0 | 0.0 | 46 ms | 0 |
| Fri 00 | 0 | 0.0 | 94 ms | 0 |
| Fri 02 | 0 | 0.0 | 65 ms | 0 |
| Fri 04 | 0 | 0.0 | 58 ms | 0 |
| Fri 05 | 0 | 0.0 | 33 ms | 0 |
| Fri 08 | 0 | 0.0 | 56 ms | 0 |
| Fri 10 | 0 | 0.0 | 85 ms | 0 |
| Fri 11 | 0 | 0.0 | 48 ms | 0 |
| Fri 12 | 0 | 0.0 | 35 ms | 0 |
| Fri 14 | 0 | 0.0 | 37 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 Replicated 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 Replicated yet. Outages of 10 minutes or more get their own page here.
Having trouble with Replicated?
One report per service every 10 minutes from this network. No account.
Follow Replicated
Get an email when Replicated goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Replicated alerts to Slack, Discord or a webhook — free.
About Replicated
We track Replicated (replicated.com) as part of the Cloud & developer group. Replicated is the platform leading software companies use to ship and manage self-hosted software at scale.
Replicated publishes an official status page at status.replicated.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 60 ms average, 33–120 ms range across 14 successful checks.
Questions
Is Replicated down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Replicated last down?
We have not recorded a public Replicated incident since monitoring began 7 days ago.
What is Replicated's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Replicated respond?
60 ms on average over the last 24 hours (33–120 ms).
Does Replicated have an official status page?
Yes, at https://status.replicated.com.
Replicated 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Replicated here at once, the problem is on Replicated'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 Replicated. 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.