outages.live
Live
RetoolIncident ·

Some antivirus products are blocking retool.app

Partial outageOfficial update
0

Some antivirus products block retool.app and stop the New app builder from loading. Retool reports the status as identified. Retool sent reclassification requests to Norton, AVG, and Avast and waits for confirmation.

State

Identified

Started

Ongoing for

7 h 23 min

Worst impact

Partial outage

Timeline

2 updates
21:3023:2101:1203:0204:53
Partial outageUpdate postedTimes in UTC

Investigating

4 h 27 min 60%

Identified

2 h 56 min 40%

Updates

Times in UTC

As posted by Retool

Identified

We've submitted requests to have the retool.app domain properly classified on all Gen Digital products (Norton, AVG, and Avast) and are waiting for confirmation that it has been removed from the blocklist.

Investigating

Some customers report that Norton, AVG, and other safe browsing vendors are flagging retool.app as dangerous and blocking it. Affected users may see a “dangerous webpage” warning or be unable to load published Retool apps or the app builder preview. Retool services are operating normally. We believe the block comes from how these products classify the domain. We are submitting reclassification requests to each vendor and following up with them. If your IT team manages these products, they may be able to add an exception for *.retool.app.

Affected components

1
New app builder

Retool in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

18

Median duration

3 h 35 min

This incident

2.1× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 3 h 35 min
90 days agoToday

Other Retool incidents

All incidents

Retool·Source Control Deployments Stalled

This incident has been resolved.

Resolved

Retool·Elevated Latency on Query Execution (Retool Cloud)

Query performance is back to normal and the incident is resolved.

Resolved

Retool·Elevated Latency on Query Execution (Retool Cloud)

This incident has been resolved.

Resolved

Retool·Retool MCP connection errors

This incident has been resolved.

Resolved

Retool·Retool MCP connection failures

This incident has been resolved.

Resolved

Follow Retool

Your coding agent knows when Retool is down, and tells you when a failure is theirs, not yours. You can also get Retool incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "retool" and tell me if Retool has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=retool
Slack
/feed subscribe https://outages.live/feed.xml?providers=retool

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane