PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Render is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Render. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Render issues today?

As of Sep 28, 2026 10:35 UTC, 0 users had reported issues with Render in the previous 24 hours.

How can I report a Render outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Render down right now?

NormalOfficial status last polled Sep 28, 2026 10:25 UTCrender.com Official status page

Render hosting, deploys, databases, networking, dashboard, and platform availability.

Are you on the Render team and see something inaccurate? Report it to us. We respond within one business day.

Is Render down right now?

No. Render has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 10:35 UTC

Normal

Render is operating normally

As of Sep 28, 2026 10:35 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 27, 2026 03:55 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Render.

Incident days

No recorded incident

6h 17m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Render. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

6h 17m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Render outage on September 27 2h 27m disruption

Sep 27, 01:27 AM → Sep 27, 03:55 AM · 2h 27m · medium

On September 27, 2026, the Render service experienced a disruption. This incident was detected by automated monitoring systems. The service disruption was resolved at 03:55 UTC on September 27, 2026.

Peak reports

in 15 min

Total reports

during outage

Duration

2h 27m

until recovery

Impact

The Render service experienced a medium-severity disruption lasting 2 hours and 27 minutes. During this period, automated monitoring indicated potential service degradation. No user-reported data was collected for this incident, as detection was solely through automated signals.

Outage timeline

Sep 27, 01:27 AM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 27, 01:27 AM
Status updated: possible issue
Sep 27, 03:55 AM
Signals cleared — incident resolved

Official updates

Sep 27, 01:27 AM
Render status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.13%

90-day uptime

99.57%

Calculated from Render's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Render: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/27/2026, 1:27:42 AM · 2h 27m

01:27 AM03:55 AM

Detection9/27/2026, 1:27:42 AM · 1d ago

Detected — medium severity

Render: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Render: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Render or have an alert rule on it can be alerted, labelled vendor-reported.

9/25/2026, 6:32:47 PM · 39 min

06:32 PM07:12 PM

Detection9/25/2026, 6:32:47 PM · 2d ago

Detected — high severity

ResolvedMedium