Runn Outage History
Runn is up right nowPingoru has recorded 15 incidents for Runn: 6 in the last 12 months and 1 in the last 90 days.
Incidents, newest first
Minor October 5, 2026 App unavailable: GraphQL requests timing out –
Started Oct 05, 2026, 12:37 PM UTC· resolved Oct 05, 2026, 12:37 PM UTC
- resolved Oct 05, 2026, 12:37 PM UTC
Runn is currently unavailable for customers hosted in our EU region. The app is failing to load, with requests timing out after around 30 seconds.
Major July 17, 2026 App unavailable: GraphQL API requests timing out 4h 47m Runn • EU • Node
Started Jul 17, 2026, 11:50 AM UTC· resolved Jul 17, 2026, 04:37 PM UTC
- investigating Jul 17, 2026, 11:50 AM UTC
Runn is currently unavailable for customers hosted in our EU region. The app is failing to load, with requests timing out after around 30 seconds. This started at approximately 12:30 UTC on 17 July. We've are actively working on a fix now.
- identified Jul 17, 2026, 04:07 PM UTC
We've identified and deployed fixes for the issues on our side, and our systems have recovered. However, some customers may still experience requests failing or pages loading without data. This remaining impact is caused by an ongoing Cloudflare incident affecting POST requests ("POST requests not succeeding", started 15:02 UTC - see cloudflarestatus.com). Cloudflare routes traffic to our EU infrastructure, so until their incident is resolved, some users' requests may not reach us at all. We're monitoring Cloudflare's incident closely and will confirm full resolution as soon as it clears.
- resolved Jul 17, 2026, 04:37 PM UTC
This incident is now resolved. Runn was unavailable for EU-hosted customers from approximately 12:30 UTC due to an issue in our API infrastructure that caused requests to time out. We deployed fixes and our systems recovered by 15:35 UTC. A separate Cloudflare incident affecting POST requests (from 15:02 UTC) continued to impact some customers after our fixes were live; Cloudflare has since implemented a fix and traffic has returned to normal. We're sorry for the disruption!
Major May 27, 2026 api.runn.io unstable 12h 4m
Started May 27, 2026, 06:51 PM UTC· resolved May 28, 2026, 06:55 AM UTC
- investigating May 27, 2026, 06:51 PM UTC
We're experiencing sporadic timeouts in our API layer, and are actively investigating
- resolved May 28, 2026, 06:55 AM UTC
This has been resolved, we are enforcing stricter rate limits on /reports/people beta API endpoints.
Major February 18, 2026 Unplanned Heroku maintenance in US region 1h 9m Runn • US • App, Runn • US • Node, Runn • US • Hasura, Runn • US • API
Started Feb 18, 2026, 02:01 AM UTC· resolved Feb 18, 2026, 03:10 AM UTC
- investigating Feb 18, 2026, 02:01 AM UTC
Our hosting provider Heroku is having issues in the US region, we're monitoring the situation. See https://status.heroku.com/incidents/2915
- resolved Feb 18, 2026, 03:10 AM UTC
Resolved
Major November 18, 2025 Cloudflare global network outage 4h 44m
Started Nov 18, 2025, 02:33 PM UTC· resolved Nov 18, 2025, 07:17 PM UTC
- resolved Nov 18, 2025, 02:33 PM UTC
The outage has been resolved, resulting in approximately two hours of downtime for the Runn application. We apologise for the inconvenience.
- investigating Nov 18, 2025, 07:17 PM UTC
Our WAF and CDN provider (Cloudflare) experienced a global network outage that affected a large amount of services including the Runn application. See https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 for details.
Major November 16, 2025 app.runn.io degraded performance 1h 38m
Started Nov 16, 2025, 09:48 PM UTC· resolved Nov 16, 2025, 11:27 PM UTC
- investigating Nov 16, 2025, 09:48 PM UTC
We are investigating intermittent loading errors in the Runn application
- resolved Nov 16, 2025, 11:27 PM UTC
We have reverted the migration which has caused this issue
Major September 28, 2025 api.runn.io and api.us.runn.io outage for 52 minutes – Runn • EU • API, Runn • US • API
Started Sep 28, 2025, 09:13 PM UTC· resolved Sep 28, 2025, 09:13 PM UTC
- resolved Sep 28, 2025, 09:13 PM UTC
api.runn.io and api.us.runn.io outage for 52 minutes
Minor July 22, 2025 api.runn.io intermittent downtime 1h 27m
Started Jul 22, 2025, 04:39 AM UTC· resolved Jul 22, 2025, 06:07 AM UTC
- identified Jul 22, 2025, 04:39 AM UTC
Likely due to upstream Heroku ACM Incident (https://status.heroku.com/incidents/2862)
- resolved Jul 22, 2025, 06:07 AM UTC
Tracked down to specific API endpoints which have been temporarily disabled
Minor April 10, 2025 Intermittent 520 Errors Messages 6d 21h Runn • EU • API, Runn • US • API
Started Apr 10, 2025, 12:04 AM UTC· resolved Apr 16, 2025, 09:28 PM UTC
- investigating Apr 10, 2025, 12:04 AM UTC
We have been made aware that some API user are experiencing a "520" error code. This has affected 617 API requests out of 1.19 million over the last 24 hrs. Approximately 0.0005% of requests. Retrying a request with a 520 should suceed on a second attempt. Please ensure your API can handle errors and will retry. This issues is being caused by our infrastructure provider's firewall (Salesforce), and we are currently waiting for furthur updates from them. We apologise for any issues this has caused with your API integrations.
- resolved Apr 16, 2025, 09:28 PM UTC
This issue was resolved by our infrastructure provider on April 11th. After monitoring for past 5 days, we can confirm the incident is now over.
Major March 5, 2025 Intermittent downtime on app.runn.io 2h
Started Mar 05, 2025, 09:02 PM UTC· resolved Mar 05, 2025, 11:03 PM UTC
- investigating Mar 05, 2025, 09:02 PM UTC
Runn started experiencing intermittent downtime of our app at approximately 19:30 UTC. Users trying to load the app would see an message "There has been an error".
- identified Mar 05, 2025, 09:04 PM UTC
At approximately 19:35 UTC we started reseting the servers which brought the back up temporarily before going down again. We contined to investigate and regularly reset the servers.
- identified Mar 05, 2025, 09:05 PM UTC
At approximately 20:15 UTC we identified a issue with our database that was causing the database not to respond.
- identified Mar 05, 2025, 09:06 PM UTC
At approximately 20:20 UTC we resolved the issue with the database, and app.runn.io appears to now be running normally.
- monitoring Mar 05, 2025, 09:09 PM UTC
We have a high degree of confident this has resolved the ongoing issue. We will continue to monitor to see if the issue re-occurs and take action. The team is working on a perment fix that would avoid this happening again. We do not expect any additional downtime before the fix is deployed, as this issue has been within the app for several month, and only caused downtime due to a unlucky combination of factors. We expect the perment fix to be released in the next several hours.
- monitoring Mar 05, 2025, 09:11 PM UTC
Note that his incident was unrelated to the incident several days ago which was caused by our hosting provider.
- resolved Mar 05, 2025, 11:03 PM UTC
We have created a permanent fix for this issue and are in the process of deploying. We consider this incident now resolved. Runn is sorry for any inconvinced caused to our customers by this incident. We will be reviewing this incident to see how we can improve our processes and avoid a similar incident in the future.
Major March 4, 2025 Short application downtime – Runn • EU • App, Runn • EU • Node, Runn • EU • Hasura, Runn • EU • API
Started Mar 04, 2025, 01:47 AM UTC· resolved Mar 04, 2025, 01:47 AM UTC
- resolved Mar 04, 2025, 01:47 AM UTC
Our host experienced issues for about 15 minutes that caused an outage for our EU servers (app.runn.io) This can be seen on our monitoring as a large spike and a drop to 99.4% availability on March 3rd 2025. This incident is resolved, however we continue to work with out host to understand the cause and how it can be mitigated by them in the future.