RunCloud logo

Is RunCloud Down?

Cloud InfrastructureLive status, outages, and incident history

Degraded. RunCloud is up but having problems.

RunCloud is reporting degraded performance as of November 14, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out RunCloud was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official RunCloud status page
How we know: the official RunCloud status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

RunCloud Status Summary

As of 16:49 UTC on 14 November 2026, RunCloud is reporting degraded performance. PulsAPI checked RunCloud's official status page and found 0 of 3 components operational, with 1 active incident. The latest incident, "Critical Linux Kernel Vulnerability - CVE-2026-98432 (CVSS 9.8)", started on Oct 29, 2026 and is still open.

Cite as: PulsAPI, “RunCloud status”, checked 14 November 2026, 16:49 UTC. https://www.pulsapi.com/services/runcloud

RunCloud Component Status

1 of 3 RunCloud components are impaired. Worst problems listed first.

1degraded2unknown
General Announcements
Degraded
RunCloud Dashboard
Unknown
RunCloud Website
Unknown

Component statuses may change independently during partial outages.

Recent RunCloud Outages & Incidents

Incident history from the official RunCloud status page, including resolution updates.

Critical Linux Kernel Vulnerability - CVE-2026-98432 (CVSS 9.8)Started Oct 29, 2026Investigating
Investigating: High Server LoadResolved Oct 22, 2026 · 4h 33mResolved
Resolved: Temporary Gateway InterruptionResolved Oct 5, 2026 · 0 minResolved

RunCloud Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a RunCloud incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% average · 3 days with incidentsNov 14

Live RunCloud Outage Reports

Problems reported by engineers using RunCloud. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No RunCloud problems reported yet.

Are you seeing RunCloud problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About RunCloud

RunCloud's status page at status.runcloud.io lists 3 components, such as General Announcements, RunCloud Dashboard (manage.runcloud.io) and RunCloud Website (runcloud.io). We read that page every few minutes and keep the incident history, so you can tell whether a problem is on RunCloud's side or yours.

RunCloud Status FAQ

Is RunCloud down right now?

The verdict at the top of this page comes from the latest poll of the official RunCloud status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if RunCloud is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until RunCloud recovers.

How do I check RunCloud uptime history?

PulsAPI tracks RunCloud uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever RunCloud changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect RunCloud outages?

PulsAPI reads the official RunCloud status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual RunCloud components?

Yes. PulsAPI monitors 3 individual RunCloud components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when RunCloud goes down?

Yes. Create a free account and subscribe to RunCloud: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with RunCloud to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot RunCloud problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor RunCloud?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so RunCloud plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track RunCloud with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services