Explo had 13 outages in the last 2 years totaling 33h 44m of downtime — averaging 0.5 incidents per month.
There were 13 Explo outages since July 8, 2025 totaling 33h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue loading the Explo Application
This Incident has been resolved
We are aware that some users are experiencing difficulty accessing their Explo instance. Explo and our DNS chain is healthy at this time. This appears to be related to a DNS resolution issue affecting certain ISPs on the user end. It is likely related to Cloudflare's outage here: https://www.cloudflarestatus.com/incidents/z3b5zxjtp6g1 We will leave this incident up for some time to help users understand the source of their access issue.
Cloudflare has now marked their incident resolved. We will be resolving this as well.
We are currently investigating email deliverability issues
This incident has been resolved.
Cloudflare has not marked the issue as follow resolved and has indicated a fix has been shipped and they are monitoring. We are going to re-open this in the monitoring state as well. Previous Explo incident: https://status.explo.co/incidents/7tstjsfrkgwp Cloudflare status: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
From the Cloudflare team: "Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency across the network." We are marking this as resolved.
Cloudflare has confirmed a global infrastructure outage. Since cloudflare serves all of Explo's traffic we're experiencing high rates of load failures and slow performance. More at https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Cloudflare is continuing to mitigate the service disruption.
Cloudflare has confirmed the issue is resolved.
We are experiencing issues with query execution due to the ongoing AWS outage. We will continue to monitor the situation and provide updates as we know more.
We are experiencing issues with query execution due to the ongoing AWS outage. We will continue to monitor the situation and provide updates as we know more.
No change from last status update. We continue to monitor closely, and will provide updates as we know more.
AWS has indicated that their services are starting to slowly recover. We are seeing that on our side as well. Updating the impact of this to minor, but will not fully resolve until AWS has given the all clear.
We have confirmed things have been resolved and AWS is back to being fully operational.
Marking this now as resolved.
We are currently investigating this issue.
We've addressed resourcing constraints causing issues and are actively monitoring for any additional issues.
Explo service is fully operational. We're continuing to instigate the root cause to avoid issues going forward.
The issue has been identified and the fix is being rolled out.
We have resolved this incident. And data querying is back to normal.
We are tracking an issue where CORS requests to the API are intermittently failing.
We have adjusted resourcing on our backend servers, which seems to have alleviated the issue. We are monitoring for any further degredation.
This incident has been resolved.
Resourcing issues for our EU data connector infrastructure instances caused degraded performance for customers who were connected in those regions. Resourcing has been adjusted to resolve any degraded performance.
Resourcing issues for our APAC and EU data connector infrastructure instances caused degraded performance for customers who were connected in those regions. Resourcing has been adjusted to resolve any degraded performance.
We are currently investigating the issue but are experiencing higher than usual load times.
We have identified some issues with an intermediary provider causing degraded performance. We're actively monitoring the issue and evaluating potential resolutions.
We are continuing to work on a fix for this issue.
We disabled some settings with our intermediary provider given their partial outage. For Explo users, things should be back to normal. We are in communication with them and will re-enable once they’ve resolved.
Marking as resolved given the previous update.
We are currently experiencing a service issue with Snowflake connections. Starting at 3:20pm ET our IP Address's for database connections (3.219.104.199 and 35.175.85.18) appear to be blocked by Snowflake resulting in intermittent access to customer data on Explo. We'll have an update for you shortly on when we expect the connection to be restored, we are currently in contact with Snowflake on this matter.
We are continuing to investigate this issue.
We've spoken with Snowflake and they are currently investigating the issue on their end. We should have an update from them in an hour and will share here accordingly.
We have identified that Snowflake incorrectly categorized certain Explo IPs under their Malicious IP Protection feature and we are working with them to re-enable access.
Snowflake connectivity issues have been resolved and they have acknowledged that Explo's IPs were incorrectly blocked.