Hosting / PaaS / Render

Render

OPERATIONAL

Since Mar 2026 · 50 incidents · status.render.com · checked just now

CompareStatus page
GradeCLast 90 days
APRODCSHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
130 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
1h 35m
LongestLongest single incident, start to resolved.
28h 52m
Since lastTime since the last counted incident was resolved.
43h 32m

By area

AProduction
6INCIDENTS
10h 37mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 31, 2026 · 2h 22mService instability in Singapore
SEV 2Sep 27, 2026 · 1h 37mObserving service instability from our upstream provider AWS in Oregon region
SEV 2Sep 24, 2026 · 0mKey Value service restarts
Most hit
Builds and Deploys4
Oregon - Builds and Deploys3
Singapore - Builds and Deploys3
Frankfurt - Builds and Deploys2
Worse. 11 in the last 6 months, 5 in the 6 before.
CShipping
11INCIDENTS
46h 16mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Aug 20, 2026 · 3h 53mDeployment Issues
SEV 2Aug 31, 2026 · 2h 22mService instability in Singapore
SEV 3Jul 27, 2026 · 28h 52mDegraded dashboard performance
Most hit
Builds and Deploys8
Oregon - Builds and Deploys7
Singapore - Builds and Deploys4
Render Dashboard3
Worse. 29 in the last 6 months, 5 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Hobby workspace, Starter instance7 of 8 cheaper · Heroku: cheaper, better grade
$21.25/mo
Starter web service (512 MB)$7
95 GB bandwidth over the 5 GB included, at $0.15/GB$14.25

render.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 37 in the last 6 months, 13 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down5
Sev 3 · Can't shipCan't deploy, build or manage it7
Sev 4 · PapercutDocs, status page, slow dashboard1

When it breaks

Start times, last 12 months, UTC.

What breaks

Builds and Deploys21 incidents
Oregon - Builds and Deploys17 incidents
Singapore - Builds and Deploys15 incidents
Frankfurt - Builds and Deploys12 incidents
Ohio - Builds and Deploys11 incidents
Virginia - Builds and Deploys11 incidents

Communication

Updates eachStatus page updates per incident, on average.
3.7Last 12 months
Update gapMedian time between status page updates during an incident.
22mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
1 of 18Sev 1–2

Incident history

Oct 20, 20263h 41mSEV 3
Deploying from GitLab may intermittently failRender deploys from GitLab intermittently failed when repository cloning broke, with deploy logs showing the clone error. Retrying a deploy could succeed. Render identified the issue, implemented a fix, and resolved the incident about 3.7 hours after it started.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Deploys pulling from GitLab intermittently failed during cloning for about 3.7 hours; retrying could succeed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 20:48 UTC · investigating
    If cloning fails, the deploy will fail. Deploy logs will provide errors related to that failure. Retrying a deploy may succeed. We are currently investigating this issue.
  2. 21:16 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 22:23 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 23:46 UTC · identified
    We are continuing to work on a fix for this issue.
  5. 00:08 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  6. 00:29 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20261h 35mSEV 3
Dashboard not updating in real time; Some Workflows SDK requests timing outAn upstream cloud provider issue stopped Render dashboard deploy and run statuses from auto-updating from about 19:10 UTC, and some Workflows SDK calls waiting for task runs failed with 500 errors after about 60 seconds. Task runs kept completing, and deploys, running services, databases and logs were unaffected. The upstream provider resolved the issue and the incident closed at 22:33 UTC.AI-graded · Render Dashboard +6
Why this grade
  1. RULES · SEV 4
    Sev 4 because Render Dashboard had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Dashboard real-time updates stalled and some Workflows SDK waits timed out with 500s; task runs kept running and deploys were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 20:58 UTC · identified
    We've identified an issue with an upstream cloud provider that is affecting real-time updates on Render. Since approximately 19:10 UTC: - Dashboard: Deploy status, service events, and service and task run statuses may not update automatically. Refresh the page to see the current state. - SDK calls that wait for a task run to finish may fail with a 500 error after about 60 seconds. The task runs themselves keep running and complete normally. To check a task run's status, use GET /v1/task-runs/{taskRunId}. Deploys, running services, databases, and logs are not affected.
  2. 21:53 UTC · monitoring
    Our upstream provider has resolved the issue, and affected Render services have recovered. We’re continuing to monitor.
  3. 22:33 UTC · resolved
    This incident has been resolved.
Source
Oct 14, 20262h 45mSEV 3
Builds, deploys, and queued deploys are not starting in all regionsA planned job scheduler upgrade included a database schema migration that drove database CPU to 100%, stalling builds and deploys in all regions on October 14. Two impact periods totaled about 2h20m. The upgrade was reverted, but a rollback clone and capacity addition failed due to cloud provider errors, and the migration kept running until terminated. Free-tier deploys were paused. Some queued deploys needed retrying. Live services were unaffected.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because Builds and Deploys had a major outage
  2. CLAUDE · SEV 3 · GLOBAL · HIGH CONFIDENCE
    Builds and deploys failed or stalled across all Render regions for about 2 hours 20 minutes; live user services were not affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
10 updates
  1. 19:32 UTC · investigating
    We are currently investigating this issue.
  2. 19:39 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 19:45 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:47 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 20:41 UTC · monitoring
    We are temporarily pausing deploys to free services.
  6. 20:55 UTC · identified
    The issue has been identified and a fix is being implemented.
  7. 20:57 UTC · identified
    Builds are failing to start again across all regions, and our team is still working to address the root cause. Deploys for free services remain paused. We'll share another update as soon as we have more information.
  8. 21:43 UTC · monitoring
    A fix has been implemented, and we are monitoring the results. Deploys and builds for services running on free instances continue to be paused.
  9. 22:18 UTC · resolved
    This incident has been resolved.
  10. 17:58 UTC · postmortem
    ### Summary On October 14, 2026, between 12:12 and 15:08 PDT \(19:12 - 22:08 UTC\), builds and deploys across all regions failed to start, stalled, or were significantly delayed during two periods of impact totaling about 2 hours and 20 minutes. The cause was a database schema migration run as part of a planned version upgrade of our internal job scheduler that coordinates builds, deploys, and other critical platform operations. The migration led to high load and a longer-than-expected recovery time of this system’s database. We will change how we perform upgrades and modifications of this system in a highly available fashion in the future so that a similar change cannot cause an outage again. ### Impact There were two periods of impact. During this time, live user services were not affected, but builds and deploys across all regions failed to start, failed to finish, or were significantly delayed. **Period 1: 12:12 - 12:40 PDT \(19:12 - 19:40 UTC\), about 28 minutes** * New builds and deploys did not start. Deploys in progress stalled. * Some requests to create a deploy through the Dashboard, API, and CLI returned errors \(HTTP 500\). **Partial recovery: 12:40 - 13:18 PDT \(19:40 - 20:18 UTC\)** * Builds and deploys ran, but deploys took about 20 seconds to start instead of a few hundred milliseconds. **Period 2: 13:18 - 15:08 PDT \(20:18 - 22:08 UTC\), about 1 hour 50 minutes** * Builds and deploys were delayed, stalled in progress \(including in pre-deploy\), or failed. From 13:51 PDT, almost no new builds were able to start. * Some queued deploys did not start after recovery, and cancelling them through the API had no effect. Users needed to retry these deploys. ### Root Cause Render uses an internal job scheduler system to coordinate builds, deploys, and other critical platform operations. We were rolling out improvements to how it distributes work, and began a planned version upgrade of this system in production after a successful practice run in a test environment. The upgrade included a database schema migration that locked a large table and drove database CPU utilization to 100%. This database stores both the system’s core job state and secondary data used for search and reporting. The system could not read or write job state reliably, so builds and deploys stopped or slowed. Engineers were alerted to the issue quickly and reverted the upgrade. However, three factors extended the impact: * A pre-upgrade step to create a database clone for rollback could not be completed due to an error from the underlying cloud provider, so a fast rollback was not available. * The migration continued to run on the database after the client performing the upgrade was stopped and the upgrade reverted. It was found and terminated at 13:49 PDT, about 1.5 hours after it started. * An attempt to add capacity to the database failed due to an error from the underlying cloud provider. ### Timeline All times are PDT on 2026-10-14 \(UTC-7\). * **12:13** - The upgrade is started, including the database schema migration. Database load rises and builds and deploys stop starting. * **12:24** - Impact to builds and deploys identified. Incident escalated. * **12:33** - Status page incident opened. * **12:34** - Engineers revert the upgrade and stop the client performing the schema migration. * **12:37** - Job scheduler system recovers. Builds and deploys resume, with slower deploy start times. End of Period 1. * **13:17** - Engineers restart one unhealthy instance of the system to rebalance load. Database connections and errors increase across the system. Start of Period 2. * **13:37** - Free-tier deploys paused to reduce load. * **13:49** - Engineers find the schema migration still running on the database and terminate it. * **14:16** - Database restarted. An attempt to add database capacity fails because of an error from the underlying cloud provider. * **14:27** - Remaining components of the system restarted. * **14:30** - Builds and deploys start to recover, with slower than usual build and deploy times as the backlog is processed. * **15:08** - Deploy start times return to normal and database load returns to pre-incident levels. End of Period 2. * **15:11** - Free-tier deploys and spin-ups gradually re-enabled. * **15:18** - Incident resolved. ### Mitigations **Completed during the incident** * Reverted the job scheduler component upgrade and configuration change \(12:34 PDT\). * Paused free-tier deploys and spin-ups to reduce load, then re-enabled them gradually after recovery. * Terminated the schema migration that was still running on the database \(13:49 PDT\). * Restarted the database and the job scheduler system to restore normal operation. * Paused the upgrade in production until the upgrade process is changed. **Ongoing \(started during the incident\)** * This database is being upgraded to support cross-zone High Availability. **Planned** * Implement a new upgrade and deployment practice for this component: we will implement blue-green deploys to avoid upgrading this system under load in the future. * Adjust the underlying storage mechanisms for the job scheduler to be better suited to this workload type, after we have implemented blue-green deploys.
PostmortemSource
Oct 3, 202646mSEV 3
Degraded Dashboard Performance; Degraded builds & deploys in OregonRender's dashboard performance was degraded and builds and deploys in the Oregon region were degraded from 19:35 to 20:21 UTC on 3 October 2026. Updates say components recovered and were monitored before the incident was resolved. The text gives no specific cause.AI-graded · regional · Render Dashboard +2
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Dashboard was slow and builds and deploys were degraded in Oregon for about 46 minutes; the update text gives no error rates.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 19:35 UTC · investigating
    We are currently investigating this issue.
  2. 19:53 UTC · investigating
    We are continuing to investigate this issue.
  3. 20:13 UTC · monitoring
    Impacted components are recovering. We are monitoring the situation.
  4. 20:21 UTC · resolved
    This incident has been resolved.
Source
Sep 27, 20261h 37mSEV 2
Observing service instability from our upstream provider AWS in Oregon regionRender services in its Oregon region were degraded for about 90 minutes because of instability at upstream provider AWS in Oregon. Web services, cron jobs, workers, builds and deploys, PostgreSQL and Redis were all affected. Services recovered by about 02:17 UTC, except the free web tier, and the incident was resolved at 03:01 UTC.AI-graded · regional · Web Services +17
Why this grade
  1. RULES · SEV 2
    Sev 2 because PostgreSQL had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Oregon services including web services, workers, PostgreSQL and Redis were degraded for about 90 minutes due to an upstream AWS issue; other regions unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 01:24 UTC · investigating
    We are currently investigating this issue.
  2. 01:36 UTC · monitoring
    Our upstream provider has begun recovering. Services in Oregon are improving, and we're continuing to monitor.
  3. 02:17 UTC · monitoring
    All services, except for the free web services tier, have recovered. We continue to monitor.
  4. 03:01 UTC · resolved
    This incident has been resolved.
Source
Sep 25, 202612mSEV 3
Build and deploy failures in OregonBuilds and deploys failed for a subset of services in Oregon for about 12 minutes; prebuilt Docker and static sites were unaffected.AI-graded · regional · Builds and Deploys +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had a partial outage
  2. CLAUDE · SEV 3 · REGIONAL · HIGH CONFIDENCE
    Builds and deploys failed for a subset of services in Oregon for about 12 minutes; prebuilt Docker and static sites were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 18:26 UTC · investigating
    We are currently investigating this issue.
  2. 18:38 UTC · resolved
    Builds and deploys failed for a subset of services in Oregon. Services using a prebuilt Docker image and static sites were unaffected.
Source
Sep 24, 20260mSEV 2
Key Value service restartsSev 2 from the incident title (no components listed)
1 update
  1. 23:30 UTC · resolved
    Around 23:31 UTC on 2026-09-23, Key Value services created prior to 2024-03-05 were inadvertently restarted due to a configuration change on our end. No further restarts are planned or expected as a result of that change.
Source
Sep 9, 202612mSEV 4
Elevated Build and Deploy Times in the Oregon RegionBuilds and deploys in Render's Oregon region had elevated times from about 21:26 to 21:38 UTC on September 9, 2026. The provider identified the issue, implemented a fix, and resolved it after about 12 minutes. No further details on cause were given.AI-graded · regional · Builds and Deploys +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · MEDIUM CONFIDENCE
    Builds and deploys in the Oregon region ran slower for about 12 minutes; the text describes no failures.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 21:26 UTC · investigating
    We are currently investigating this issue.
  2. 21:31 UTC · investigating
    We are continuing to investigate this issue.
  3. 21:32 UTC · investigating
    We are continuing to investigate this issue.
  4. 21:34 UTC · identified
    The issue has been identified and a fix is being implemented.
  5. 21:38 UTC · resolved
    This incident has been resolved.
Source
Sep 2, 202621mSEV 3
Degraded builds/deploysBuilds and deploys were degraded across all five Render regions for about 21 minutes; the text gives no failure rate.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had a partial outage
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Builds and deploys were degraded across all five Render regions for about 21 minutes; the text gives no failure rate.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 17:19 UTC · investigating
    We are currently investigating this issue.
  2. 17:30 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 17:40 UTC · resolved
    This incident has been resolved.
Source
Aug 31, 20260mSEV 2
Some Web services in Oregon unavailableSev 2 from the incident title (no components listed)
1 update
  1. 19:30 UTC · resolved
    Some web services in Oregon were unavailable between 19:20 and 19:30 UTC.
Source
Aug 31, 20262h 22mSEV 2
Service instability in SingaporeSome Render web services in Singapore had unexpected restarts and intermittent availability, and inbound traffic was impacted. Deploys were primarily affected. Free service spin-ups from idle were temporarily disabled. A fix was implemented and the incident was resolved after about 2h20m.AI-graded · regional · Web Services +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Builds and Deploys had a major outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some Singapore web services restarted or were intermittently unavailable and deploys failed for about two and a half hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 15:47 UTC · investigating
    We are investigating service instability affecting some web services in our Singapore region. Customers may experience unexpected service restarts or intermittent availability. Our team is actively investigating and working to restore normal operation. We will provide an update as more information becomes available.
  2. 16:08 UTC · investigating
    We've observed that deploys are primarily affected by this.
  3. 16:33 UTC · investigating
    Inbound traffic to Singapore services is impacted. Free service spin-ups (from idle) in Singapore have been temporarily disabled while we continue to investigate.
  4. 17:22 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  5. 18:09 UTC · resolved
    This incident has been resolved.
Source
Aug 20, 20263h 53mSEV 2
Deployment IssuesRender builds and deploys failed in all regions from about 15:47 to 17:45 UTC on Aug 20 due to an upstream Google Cloud issue. Free web service builds, deploys and spin-up were disabled during mitigation, then re-enabled. Some customers saw elevated latency during recovery. Render reported full recovery and resolved the incident at 19:40 UTC.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had a partial outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Builds and deploys failed across all Render regions for about two hours due to a Google Cloud issue; free web service spin-up was also disabled.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 15:47 UTC · investigating
    We are currently investigating this issue.
  2. 16:12 UTC · identified
    An issue has been identified with our upstream provider, Google Cloud. Free Web Services: Builds/deploys and spin-up have been temporarily disabled while we work to mitigate the issue.
  3. 17:27 UTC · monitoring
    We are observing recovery for builds and deploys in all regions. Builds, deploys, and spin-up for free web services have been re-enabled. Some customers may continue to see elevated latency while recovery progresses. We are continuing to monitor.
  4. 17:45 UTC · monitoring
    We have observed full recovery. We are continuing to monitor for any further issues.
  5. 19:40 UTC · resolved
    This incident has been resolved.
Source
Jul 27, 202628h 52mSEV 3
Degraded dashboard performanceRender's dashboard was slow from July 27 and the REST API saw timeouts requiring retries. Deploy failure reasons were temporarily unavailable. A fix was deployed, and the incident was resolved July 28 after deploy failure reasons were re-enabled. Customer apps were not described as affected.AI-graded · Render Dashboard +1
Why this grade
  1. RULES · SEV 3
    Sev 3 because Render REST API had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Dashboard was slow and REST API requests timed out for about a day; deploy failure reasons were disabled until resolved.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 14:43 UTC · investigating
    Requests through the dashboard may be slower than usual. We're currently investigating the issue.
  2. 16:20 UTC · investigating
    We are continuing to investigate this issue.
  3. 17:59 UTC · investigating
    We are continuing to investigate this issue.
  4. 18:27 UTC · investigating
    The REST API is also experiencing degraded performance. As a result, requests to it may experience timeouts and you may need to retry your request. We are continuing to investigate.
  5. 20:18 UTC · monitoring
    We've implemented a fix and are monitoring the results. Deploy failure reasons will be temporarily unavailable. Deploy failure events will still be generated. We will provide an update once deploy failure reasons are re-enabled.
  6. 23:58 UTC · monitoring
    No further issues have been observed since our fixes. The Dashboard and REST API remain fully operational. Deploy failure reasons are still disabled. We will update this incident once they are re-enabled. There are no further updates expected for today (2026-07-27, UTC-7).
  7. 19:35 UTC · resolved
    We've continued to observe no further issues and deploy failure reasons have been re-enabled.
Source
Jul 24, 20262h 14mSEV 2
Service Disruption in OregonRender's Oregon region had an infrastructure issue starting 11:16 UTC on 24 July 2026 that left some web services unreachable or returning failed requests. Recovery was seen by 11:27 UTC and the incident was resolved at 13:30 UTC. Render said an upstream provider likely caused it; no further detail was given.AI-graded · regional · Web Services +1
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Web services in the Oregon region were unreachable or failing requests for about two hours; other regions were not mentioned as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 11:16 UTC · investigating
    We are investigating an infrastructure issue affecting services hosted in our Oregon region. Some services may be unreachable or experience failed requests. Our engineering team is actively working to identify the cause and restore normal operation.
  2. 11:27 UTC · monitoring
    We've observed recovery across all services and are now monitoring the situation.
  3. 11:44 UTC · monitoring
    We believe the issue was caused by an upstream provider. We're continuing to monitor the situation.
  4. 13:30 UTC · resolved
    This incident has now been resolved.
Source
Jul 20, 20261h 30mSEV 3
Degraded builds/deploys (all regions)Render builds and deploys failed in all regions from about 00:41 to 02:11 UTC on July 20, 2026. Authentication failures when deploying from GitHub repositories were caused by a GitHub outage. Render said build failure rates recovered and resolved the incident.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · HIGH CONFIDENCE
    Builds and deploys failed across all Render regions for about 90 minutes due to GitHub authentication failures during a GitHub outage.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 00:41 UTC · investigating
    We are currently investigating this issue.
  2. 00:55 UTC · identified
    GitHub continues to report an outage, https://www.githubstatus.com. This is causing authentication failures when trying to deploy from a GitHub repository.
  3. 01:54 UTC · monitoring
    We are now seeing a recovery in our build failure rate. We are continuing to monitor the issue.
  4. 02:11 UTC · resolved
    Builds failure rates have recovered. Resolving.
Source
Jul 19, 20265h 36mSEV 2
GitHub git clone 403 errorsDeploys for services in Render's Frankfurt region failed because git clones from GitHub returned 403 errors, starting around 03:44 UTC on 19 July. Running services were not affected. Deployments returned to normal from about 08:40 UTC, and the incident was resolved at 09:20 UTC. The provider worked with GitHub on the cause, which the update does not state.AI-graded · regional · Builds and Deploys +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Builds and Deploys had a major outage
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Git-based deploys failed with 403 errors for services in Frankfurt for about five hours; running services and other regions were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 03:44 UTC · investigating
    We have received an elevated number of reports about git clone failures resulting in a 403 error, aborting the deployment. We are investigating.
  2. 03:55 UTC · identified
    Services failing to deploy are those deployed in Frankfurt. Running services are not affected, only the deploy process is failing. We are still working to determine the cause of this error for those services.
  3. 05:57 UTC · identified
    Users with services hosted in Frankfurt that rely on GitHub repositories for deployments continue to see 403 errors in their logs causing the deployment to fail. We are continuing to work on this issue within our own systems and have reached out to GitHub.
  4. 08:29 UTC · identified
    We are continuing to work towards mitigating this issue, while also working with GitHub to resolve these deployment failures.
  5. 09:10 UTC · monitoring
    Deployments have been consistently completing since approximately 08:40, and are returning to normal levels. We are monitoring for any other impacts.
  6. 09:20 UTC · resolved
    This incident has been resolved.
Source
Jul 16, 20261h 33mSEV 3
GitHub outage affecting new service creation and service deploysRender reported that new service creation and service deploys were affected by a GitHub REST API degradation across its build regions in Oregon, Frankfurt, Ohio, Singapore and Virginia. The incident began at 22:42 UTC on July 16 and was resolved at 00:14 UTC on July 17, after GitHub mitigated its incident. Running services were not described as affected.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because Builds and Deploys had a major outage
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Creating new services and deploying failed across Render's build regions for about 90 minutes due to a GitHub REST API outage.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 22:42 UTC · investigating
    We are currently investigating this issue.
  2. 22:42 UTC · investigating
    We are continuing to investigate this issue.
  3. 23:09 UTC · identified
    GitHub has updated its status page to report degraded REST API availability: https://www.githubstatus.com/incidents/gxycch3076xk
  4. 00:13 UTC · monitoring
    GitHub reports that they have mitigated their incident and are monitoring to ensure stability.
  5. 00:14 UTC · resolved
    This incident has been resolved.
Source
Jul 15, 20261h 06mSEV 3
Some users enrolled in 2FA are experiencing login issuesSome Render users with two-factor authentication enabled got stuck in login loops when accessing the dashboard. A fix was implemented and the incident was resolved about 65 minutes after it started. The text does not describe impact on running apps or deploys.AI-graded · some customers · Render Dashboard
Why this grade
  1. RULES · SEV 3
    Sev 3 because Render Dashboard had a partial outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Some 2FA-enrolled users were stuck in login loops on the Render dashboard for about an hour; other users were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 21:50 UTC · investigating
    Some users enrolled in 2FA report login loops when attempting to access the Render dashboard. We're investigating.
  2. 21:55 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 22:06 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 22:56 UTC · resolved
    This incident has been resolved.
Source
Jul 15, 202632mSEV 3
Render Dashboard UnavailableRender Dashboard was unavailable for about 30 minutes; the text does not say whether deploys or customer apps were affected.AI-graded · Render Dashboard
Why this grade
  1. RULES · SEV 3
    Sev 3 because Render Dashboard had a major outage
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Render Dashboard was unavailable for about 30 minutes; the text does not say whether deploys or customer apps were affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 00:22 UTC · investigating
    We are currently investigating an issue with the availability of the Render Dashboard.
  2. 00:51 UTC · monitoring
    We have identified the root cause of this issue and have made a change to resolve it. Our dashboard is back online. We are now monitoring the issue to ensure it is fully resolved.
  3. 00:54 UTC · resolved
    This issue has been resolved.
Source
Jul 9, 202626mSEV 2
Some services and datastores in Singapore experiencing brief disruptionsWeb services, workers, cron jobs, PostgreSQL and Redis in Singapore had brief disruptions for about 26 minutes; other regions were not listed as affected.AI-graded · regional · Web Services +11
Why this grade
  1. RULES · SEV 1
    Sev 1 because PostgreSQL had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Web services, workers, cron jobs, PostgreSQL and Redis in Singapore had brief disruptions for about 26 minutes; other regions were not listed as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 18:18 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  2. 18:44 UTC · resolved
    This incident has been resolved.
Source
Jul 2, 202650mSEV 4
Delayed wildcard issuance or renewalWildcard certificate issuance and renewal were slow for about 50 minutes due to an upstream Let's Encrypt incident.AI-graded · some customers · Custom Domains
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Wildcard certificate issuance and renewal were slow for about 50 minutes due to an upstream Let's Encrypt incident.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 19:09 UTC · identified
    Due to an ongoing LetsEncrypt incident, wildcard certificates may be slow to issue/renew. We are actively monitoring the situation.
  2. 19:59 UTC · resolved
    Issuance has returned to expected performance and we've observed no further impact.
Source
Jun 23, 20261h 45mSEV 2
External connections to Postgres services may terminate intermittentlyExternal connections to Postgres services in five regions, including Oregon, Frankfurt, Ohio, Singapore and Virginia, terminated intermittently. Render rolled out a fix and resolved the incident after about two hours. The provider noted customers may have seen impact from June 22, 2026, at 11:50 UTC.AI-graded · PostgreSQL +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because PostgreSQL had degraded performance
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    External connections to Postgres databases terminated intermittently in five regions for about two hours; not a full outage.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 00:00 UTC · investigating
    We are currently investigating this issue.
  2. 00:32 UTC · monitoring
    We have rolled out a fix for this issue and are now monitoring it before confirming the resolution.
  3. 01:44 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 01:45 UTC · resolved
    This has now been resolved. Customers will have seen an impact from Jun 22, 2026, at 11:50 UTC.
Source
Jun 18, 20263h 11mSEV 3
Slow/failing wildcard certificates related to LetsEncrypt incidentWildcard certificate issuance was slow or failing for about three hours due to an upstream Let's Encrypt incident; other functions were not described as affected.AI-graded · some customers · Custom Domains
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Wildcard certificate issuance was slow or failing for about three hours due to an upstream Let's Encrypt incident; other functions were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 21:06 UTC · identified
    We are seeing slow or failing issuance of wildcard certificates due to an ongoing incident with the LetsEncrypt certificate authority. We are actively monitoring the situation on our end.
  2. 23:15 UTC · monitoring
    We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.
  3. 00:17 UTC · resolved
    We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.
Source
Jun 11, 202650mSEV 3
Stuck queued deploysDeploys across five regions got stuck in queue starting 19:42 UTC on June 11, 2026. Render gave a workaround: set the overlapping deploy policy to Override, redeploy, then set it back to Wait. A fix was applied around 19:59 UTC and the incident was resolved at 20:32 UTC.AI-graded · some customers · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · HIGH CONFIDENCE
    Deploys queued and got stuck across Oregon, Frankfurt, Ohio, Singapore and Virginia for about 50 minutes; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 19:42 UTC · investigating
    We are currently investigating the problem. Try this work-around to get deploys going again: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to "Wait"
  2. 19:59 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 20:32 UTC · resolved
    This incident has been resolved. If you still have a stuck queued deploy, follow the instructions below under "Investigating" to clear the queue. It should then work again as expected going forward.
Source
Jun 11, 202621mSEV 3
Failed or delayed autodeploysAutodeploys failed or were delayed across Render's build and deploy systems in five regions for about 21 minutes.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Autodeploys failed or were delayed across Render's build and deploy systems in five regions for about 21 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:56 UTC · investigating
    We are currently investigating this issue.
  2. 19:06 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 19:17 UTC · resolved
    This incident has been resolved.
Source
Jun 11, 20262h 11mSEV 3
Queued deploys stuckQueued deploys stalled across Builds and Deploys in five regions for about two hours; running apps were not described as affected.AI-graded · regional · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Queued deploys stalled across Builds and Deploys in five regions for about two hours; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 16:01 UTC · identified
    The earlier "Platform latency" incident has affected queued deploys. We are implementing a fix
  2. 16:44 UTC · identified
    We are continuing to work on a fix for this issue. In the meantime, stuck deploys can be cleared with these steps: * Go into Workspace Settings * Change the Overlapping Deploy Policy to "Override" * Initiate a new deploy (which will then cancel the stuck deploy) * Change the Deploy Policy back to "Wait"
  3. 18:12 UTC · resolved
    This incident has been resolved.
Source
Jun 11, 202620mSEV 3
Platform latencyBuilds, deploys and webhooks were delayed across all five regions for about 20 minutes; auto-deploys were missed and need retriggering.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Builds, deploys and webhooks were delayed across all five regions for about 20 minutes; auto-deploys were missed and need retriggering.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 14:37 UTC · investigating
    We are currently investigating delays across the platform affecting builds, deploys, and webhooks.
  2. 14:56 UTC · monitoring
    A fix has been implemented, and we are continuing to monitor. Auto-deploys would have been affected/missed by these delays and will need to be retriggered.
  3. 14:57 UTC · resolved
    This incident has been resolved.
Source
Jun 9, 20261h 08mSEV 3
Delayed/missing autodeploysAutodeploys were delayed or missing for about 68 minutes across builds and deploys in all five regions; apps still served traffic.AI-graded · Builds and Deploys +5
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds and Deploys had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Autodeploys were delayed or missing for about 68 minutes across builds and deploys in all five regions; apps still served traffic.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 20:01 UTC · investigating
    We are currently investigating this issue.
  2. 20:55 UTC · monitoring
    We're seeing evidence of recovery and are continuing to monitor the situation.
  3. 21:09 UTC · resolved
    This incident has been resolved.
Source
Jun 5, 202653mSEV 3
Issues with GitHub connectionsSev 3 from the incident title (no components listed)
3 updates
  1. 16:21 UTC · investigating
    We are currently investigating this issue.
  2. 16:48 UTC · monitoring
    We're seeing signs of recovery. Please try redeploying any affected services.
  3. 17:14 UTC · resolved
    This incident has been resolved.
Source
Jun 4, 20261h 12mSEV 3
Emails, including notifications, are delayedSev 3 because Render Dashboard had a partial outageRender Dashboard
4 updates
  1. 23:27 UTC · investigating
    We are currently investigating this issue.
  2. 23:38 UTC · monitoring
    Our email provider is experiencing delays in sending emails. Emails will still be delivered after that delay. This impacts verification emails and notifications for workspaces or services. We're monitoring the situation.
  3. 23:43 UTC · monitoring
    Our provider has resolved the delay and backlogged emails are being processed. We're continuing to monitor.
  4. 00:39 UTC · resolved
    Outstanding emails have been sent and processing has returned to expected operation.
Source
Jun 1, 202620mSEV 4
Unable to load metrics for some services in OregonSev 4 because Metrics/Logs had a partial outageMetrics/Logs +1
3 updates
  1. 21:25 UTC · investigating
    We are currently investigating this issue. It affects metrics only. Logs are unaffected.
  2. 21:32 UTC · monitoring
    We're seeing recovery and are monitoring.
  3. 21:45 UTC · resolved
    This incident has been resolved.
Source
May 22, 202644mSEV 3
Upstream provider outage causing delays provisioning custom domainsSev 3 from the incident title (no components listed)Custom Domains
3 updates
  1. 15:53 UTC · investigating
    We are currently investigating this issue.
  2. 16:25 UTC · monitoring
    Our upstream provider has deployed a fix and we're seeing gradual recovery.
  3. 16:37 UTC · resolved
    Our upstream provider has resolved the issue and custom domain provisioning has recovered.
Source
May 20, 202656mSEV 2
Investigating Intermittent Postgres Connectivity Issues in the Oregon RegionSev 2 because PostgreSQL had degraded performancePostgreSQL +1
4 updates
  1. 18:01 UTC · investigating
    We are currently investigating this issue.
  2. 18:17 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 18:23 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 18:57 UTC · resolved
    This incident has been resolved.
Source
May 12, 20260mSEV 3
Logs unavailable for some services in all regionsSev 3 from the incident title (no components listed)
1 update
  1. 20:00 UTC · resolved
    Between approximately 19:45 UTC and 20:30 UTC, logs may be unavailable in the Dashboard. For logs that are unavailable, logs were not streamed to third-party logging providers.
Source
May 11, 202611mSEV 3
Degraded builds/deploys (all regions)Sev 3 because Builds and Deploys had degraded performanceBuilds and Deploys +5
3 updates
  1. 17:07 UTC · investigating
    We are currently investigating this issue.
  2. 17:11 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 17:18 UTC · resolved
    This incident has been resolved.
Source
May 8, 202644mSEV 3
Certificate issuance paused for Let's EncryptSev 3 from the incident title (no components listed)Custom Domains
2 updates
  1. 20:22 UTC · monitoring
    Due to an ongoing incident, Let's Encrypt has paused all certificate issuance. This primarily impacts wildcard domains on Render. In rare instances, non-wildcard custom domains may be using Let's Encrypt for their certificates.
  2. 21:06 UTC · resolved
    Let's Encrypt has resumed certificate issuance.
Source
May 7, 202654mSEV 1
HA Postgres UnavailabilitySev 1 because PostgreSQL had a partial outagePostgreSQL +11
8 updates
  1. 02:00 UTC · investigating
    We're investigating reports of Postgres unavailability in multiple regions. At this point we believe this only impacts databases with HA turned on.
  2. 02:01 UTC · investigating
    We are continuing to investigate this issue.
  3. 02:07 UTC · investigating
    We are continuing to investigate this issue.
  4. 02:21 UTC · identified
    We've identified the issue and are implementing a fix.
  5. 02:34 UTC · identified
    We're bringing the affected Postgres instances back online and expect full recovery within fifteen minutes.
  6. 02:38 UTC · identified
    We're continuing to see instance recovery across the fleet. Render Workflows is now fully operational.
  7. 02:47 UTC · identified
    All affected instances are back online, though a few databases may still show a stale 'Unready' status. We are working to refresh the status.
  8. 02:54 UTC · resolved
    Everything is back to normal, and the incident is now resolved. We are planning long-term mitigations to prevent this issue from recurring, and we will share the results of our investigation with all affected customers.
Source
Apr 23, 202630mSEV 3
Delayed deployment for new services in Oregon regionSev 3 from the incident title (no components listed)Web Services +1
4 updates
  1. 16:51 UTC · investigating
    We are investigating an issue where new services created in the Oregon region are taking longer than usual to deploy.
  2. 16:59 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 17:06 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 17:21 UTC · resolved
    This incident has been resolved.
Source
Apr 16, 202614mSEV 1
Some web services and databases in Oregon are unresponsiveSev 1 because PostgreSQL had a partial outageWeb Services +3
2 updates
  1. 23:36 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  2. 23:51 UTC · resolved
    This incident has been resolved.
Source
Apr 14, 20261h 33mSEV 4
BitBucket account connection issuesSev 4 because Render Dashboard had degraded performanceRender Dashboard
3 updates
  1. 14:31 UTC · investigating
    We are currently investigating reports of issues connecting BitBucket accounts/repos to Render. Existing services configured with a BitBucket repo are unaffected.
  2. 15:12 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 16:04 UTC · resolved
    This incident has been resolved.
Source
Apr 13, 202624mSEV 3
Image pull failures in OregonSev 3 because Builds and Deploys had a partial outageBuilds and Deploys +1
3 updates
  1. 22:03 UTC · identified
    We are seeing image pull failures within the Oregon region. We have identified the problem and are working on a fix.
  2. 22:18 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 22:26 UTC · resolved
    This incident has been resolved.
Source
Apr 10, 202615mSEV 2
Infrastructure maintenance operations are currently in progress for outbound IPs in the Oregon regionSev 2 from the incident title (no components listed)
2 updates
  1. 14:41 UTC · investigating
    Ongoing maintenance is underway for static IPs in the Oregon region. Services in this region may experience changes to their outbound IP ranges.
  2. 14:56 UTC · resolved
    The maintenance has been completed successfully.
Source
Apr 8, 20260mSEV 2
Delays in stateful service creation in OregonSev 2 from the incident title (no components listed)
1 update
  1. 12:30 UTC · resolved
    Between 12:40 UTC and 18:10 UTC, creation of stateful services in Oregon was delayed. Stateful services are any of Postgres, Key Value, or services with a persistent disk.
Source
Apr 8, 202612h 14mSEV 2
Disruption affecting the provisioning of new instances in Singapore and partially in OregonSev 2 because Cron Jobs had a major outageWeb Services +14
13 updates
  1. 09:57 UTC · investigating
    This issue may affect new instances during builds, scaling, and similar operations. You may experience build/deploy failures. We are still investigating.
  2. 10:31 UTC · investigating
    We have temporarily disabled free services in Singapore. We are continuing to investigate and work to mitigate the issue.
  3. 10:54 UTC · investigating
    We are seeing some recovery following our mitigation efforts, but we are still working to identify the root cause for a long-term resolution.
  4. 11:22 UTC · investigating
    We are continuing to investigate this issue.
  5. 11:23 UTC · identified
    Services with paid compute should now be operating normally. Please note that free services in this region are still intermittently disabled.
  6. 14:42 UTC · identified
    We are now seeing the same issue affecting services in Oregon partially. We are investigating to remediate this as quickly as possible.
  7. 15:02 UTC · identified
    We are continuing to work on a fix for this issue.
  8. 15:02 UTC · monitoring
    We're seeing recovery across all regions.
  9. 16:05 UTC · monitoring
    We are disabling new free services in Singapore and partially in Oregon.
  10. 18:08 UTC · monitoring
    We are continuing to monitor for any further issues.
  11. 18:48 UTC · monitoring
    Paid services are continuing to see recovery across builds and deploys. Free services remain disabled and will return errors if loaded in a browser. Singapore and part of Oregon remain impacted.
  12. 19:44 UTC · monitoring
    Provisioning is recovering for free and paid services across all regions. Free services have resumed serving traffic. We are continuing to monitor for further issues.
  13. 22:11 UTC · resolved
    We've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.
Source
Apr 7, 20260mSEV 4
Unable to view workflows in the DashboardSev 4 from the incident title (no components listed)
1 update
  1. 18:00 UTC · resolved
    Between 18:04 and 19:10 UTC, workflows were unable to be viewed in the Dashboard. All workflows continued to run and were otherwise operational. This issue has been resolved.
Source
Mar 25, 202629h 05mSEV 1
Some Render Workflows tasks are not being scheduledSev 1 from the incident title (no components listed)Workflows +1
5 updates
  1. 14:45 UTC · investigating
    We are working on resolving the issue.
  2. 16:40 UTC · identified
    The issue has been identified, and there should be no issues scheduling tasks at this time. We are still working to ensure it is fully resolved.
  3. 17:54 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:51 UTC · resolved
    This issue is now resolved. A full RCA will be available in the incident page within the next two weeks.
  5. 13:23 UTC · postmortem
    Affected customers have been contacted directly. If you would like more details, please contact support at [[email protected]](mailto:[email protected]) or reach out through the chat widget in the Render dashboard.
PostmortemSource
Mar 24, 202622mSEV 4
Some users may experience delayed logs in the Oregon regionSev 4 because Metrics/Logs had degraded performanceMetrics/Logs +1
3 updates
  1. 13:09 UTC · identified
    The issue has been identified, and we are already monitoring recovery.
  2. 13:12 UTC · monitoring
    We are monitoring recovery.
  3. 13:31 UTC · resolved
    The issue is fixed.
Source
Mar 13, 20262h 16mSEV 3
Degraded builds and deployments in the Singapore regionSev 3 because Builds and Deploys had degraded performanceBuilds and Deploys +1
3 updates
  1. 15:51 UTC · investigating
    We are observing a recurrence of the previous incident (https://status.render.com/incidents/d9k4p51v1y7g). The current impact appears to be significantly lower. We are proactively investigating and closely monitoring the situation internally to ensure minimal impact on users.
  2. 15:53 UTC · monitoring
    We are currently monitoring.
  3. 18:07 UTC · resolved
    This incident has been resolved.
Source
Mar 13, 20262h 17mSEV 2
Degraded builds and deployments in the Singapore regionSev 2 because Builds and Deploys had a major outageBuilds and Deploys +3
4 updates
  1. 08:52 UTC · investigating
    Builds and deployments in the Singapore region are currently experiencing degraded performance. You may notice longer than usual completion times.
  2. 09:27 UTC · investigating
    We have disabled services using free instance types in the Singapore region
  3. 10:18 UTC · monitoring
    We have re-enabled services using the free instance types in the Singapore region and are currently monitoring the impact.
  4. 11:09 UTC · resolved
    We believe this incident has been successfully mitigated. If you continue to experience any issues, please contact [email protected].
Source
Mar 9, 202620mSEV 1
Custom domains are unable to be createdSev 1 from the incident title (no components listed)Custom Domains
2 updates
  1. 20:19 UTC · investigating
    We are currently investigating this issue.
  2. 20:39 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up26 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.31% up27 incidentsMTTR 55m~$12/mo

README badge

Render's live grade, for your README.

Render grade badge
[![render on downagain.dev](https://downagain.dev/badge/render.svg)](https://downagain.dev/p/render)