Explo Outage History

Explo is up right now

Pingoru has recorded 43 incidents for Explo: 6 in the last 12 months and 0 in the last 90 days.

Source: status.explo.co

43incidents recorded
6last 12 months
0last 90 days
90 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Explo in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202600 of 744 (0%)
June 202610 of 720 (0%)
July 202612 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 550 (0%)

Incidents, newest first

Notice July 17, 2026 Intermittent Auth and dashboard load issues 1h 59m Explo Dashboards, Explo Report Builder

Started Jul 17, 2026, 02:59 PM UTC· resolved Jul 17, 2026, 04:59 PM UTC

  1. investigating Jul 17, 2026, 02:59 PM UTC

    We are currently investigating an issue where login auth and dashboard loads are getting intermittently affected.

  2. identified Jul 17, 2026, 03:10 PM UTC

    We are experiencing issues with our provider Cloudflare that is reporting issues with their requests. More information on their incident here: https://www.cloudflarestatus.com/incidents/652w59bvnbsj

  3. resolved Jul 17, 2026, 04:59 PM UTC

    Incident is resolved in Cloudflare and we are actively monitoring if there are any additional Explo issues

Read the full incident report →

Notice June 2, 2026 Intermittent loading issues on the Explo Application 18m Explo Dashboards, Explo Report Builder

Started Jun 02, 2026, 02:50 PM UTC· resolved Jun 02, 2026, 03:09 PM UTC

  1. investigating Jun 02, 2026, 02:50 PM UTC

    We are currently investigating an issue loading the Explo Application

  2. resolved Jun 02, 2026, 03:09 PM UTC

    This Incident has been resolved

Read the full incident report →

Notice April 17, 2026 DNS Resolution Issues for Some Users caused by their ISP 27m Explo Dashboards, Explo Report Builder

Started Apr 17, 2026, 08:10 PM UTC· resolved Apr 17, 2026, 08:38 PM UTC

  1. monitoring Apr 17, 2026, 08:10 PM UTC

    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.

  2. resolved Apr 17, 2026, 08:38 PM UTC

    Cloudflare has now marked their incident resolved. We will be resolving this as well.

Read the full incident report →

Minor February 5, 2026 Scheduled Emails Not Sending 14m Exports: Email delivery

Started Feb 05, 2026, 05:49 PM UTC· resolved Feb 05, 2026, 06:04 PM UTC

  1. investigating Feb 05, 2026, 05:49 PM UTC

    We are currently investigating email deliverability issues

  2. resolved Feb 05, 2026, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 Global Explo outage due to CDN issues (reopened) 3h 1m Explo Dashboards, Customer Data Access, Customer Data Access, Dashboard Embeds and 9 more

Started Nov 18, 2025, 03:41 PM UTC· resolved Nov 18, 2025, 06:42 PM UTC

  1. monitoring Nov 18, 2025, 03:41 PM UTC

    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

  2. resolved Nov 18, 2025, 06:42 PM UTC

    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.

Read the full incident report →

Major November 18, 2025 Global Explo outage due to CDN issues 3h Explo Dashboards, Customer Data Access, Customer Data Access, Dashboard Embeds and 9 more

Started Nov 18, 2025, 11:50 AM UTC· resolved Nov 18, 2025, 02:50 PM UTC

  1. investigating Nov 18, 2025, 12:16 PM UTC

    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

  2. investigating Nov 18, 2025, 02:07 PM UTC

    Cloudflare is continuing to mitigate the service disruption.

  3. resolved Nov 18, 2025, 02:50 PM UTC

    Cloudflare has confirmed the issue is resolved.

Read the full incident report →

Notice October 20, 2025 Degraded Query Execution Performance 19h 59m Customer Data Access, Dashboard Embeds, Report Builder Embeds, Tabular Exports

Started Oct 20, 2025, 05:00 AM UTC· resolved Oct 21, 2025, 12:59 AM UTC

  1. investigating Oct 20, 2025, 04:35 PM UTC

    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.

  2. investigating Oct 20, 2025, 04:43 PM UTC

    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.

  3. investigating Oct 20, 2025, 06:31 PM UTC

    No change from last status update. We continue to monitor closely, and will provide updates as we know more.

  4. investigating Oct 20, 2025, 09:57 PM UTC

    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.

  5. investigating Oct 21, 2025, 12:58 AM UTC

    We have confirmed things have been resolved and AWS is back to being fully operational.

  6. resolved Oct 21, 2025, 12:59 AM UTC

    Marking this now as resolved.

Read the full incident report →

Notice October 3, 2025 Degraded performance across Explo app and Embeds 6m Explo Dashboards, Customer Data Access, Dashboard Embeds, Explo Report Builder and 4 more

Started Oct 03, 2025, 08:58 PM UTC· resolved Oct 03, 2025, 09:05 PM UTC

  1. investigating Oct 03, 2025, 08:58 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 03, 2025, 09:02 PM UTC

    We've addressed resourcing constraints causing issues and are actively monitoring for any additional issues.

  3. resolved Oct 03, 2025, 09:05 PM UTC

    Explo service is fully operational. We're continuing to instigate the root cause to avoid issues going forward.

Read the full incident report →

Notice September 30, 2025 Degraded Data Querying 8m Customer Data Access, Dashboard Embeds, Report Builder Embeds

Started Sep 30, 2025, 06:20 PM UTC· resolved Sep 30, 2025, 06:28 PM UTC

  1. identified Sep 30, 2025, 06:20 PM UTC

    The issue has been identified and the fix is being rolled out.

  2. resolved Sep 30, 2025, 06:28 PM UTC

    We have resolved this incident. And data querying is back to normal.

Read the full incident report →

Major September 16, 2025 Degraded access to API 56m Explo Dashboards, Explo Report Builder

Started Sep 16, 2025, 08:15 PM UTC· resolved Sep 16, 2025, 09:11 PM UTC

  1. investigating Sep 16, 2025, 08:15 PM UTC

    We are tracking an issue where CORS requests to the API are intermittently failing.

  2. monitoring Sep 16, 2025, 08:45 PM UTC

    We have adjusted resourcing on our backend servers, which seems to have alleviated the issue. We are monitoring for any further degredation.

  3. resolved Sep 16, 2025, 09:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 15, 2025 Degraded performance in EU FIDO Instances –

Started Aug 15, 2025, 06:00 AM UTC· resolved Aug 15, 2025, 06:00 AM UTC

  1. resolved Aug 15, 2025, 07:18 PM UTC

    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.

Read the full incident report →

Minor August 13, 2025 Degraded performance in APAC and EU FIDO Instances –

Started Aug 13, 2025, 06:00 PM UTC· resolved Aug 13, 2025, 06:00 PM UTC

  1. resolved Aug 15, 2025, 07:05 PM UTC

    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.

Read the full incident report →

Notice July 10, 2025 Latency issues due to higher than usual traffic to Explo application 35m Explo Dashboards, Customer Data Access, Dashboard Embeds, Explo Report Builder and 2 more

Started Jul 10, 2025, 08:04 PM UTC· resolved Jul 10, 2025, 08:39 PM UTC

  1. investigating Jul 10, 2025, 08:04 PM UTC

    We are currently investigating the issue but are experiencing higher than usual load times.

  2. identified Jul 10, 2025, 08:18 PM UTC

    We have identified some issues with an intermediary provider causing degraded performance. We're actively monitoring the issue and evaluating potential resolutions.

  3. identified Jul 10, 2025, 08:37 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Jul 10, 2025, 08:38 PM UTC

    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.

  5. resolved Jul 10, 2025, 08:39 PM UTC

    Marking as resolved given the previous update.

Read the full incident report →

Notice July 8, 2025 Intermittent Access for Snowflake Users 4h 54m Explo Dashboards, Customer Data Access, Dashboard Embeds, Explo Report Builder and 2 more

Started Jul 08, 2025, 08:25 PM UTC· resolved Jul 09, 2025, 01:20 AM UTC

  1. investigating Jul 08, 2025, 08:25 PM UTC

    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.

  2. investigating Jul 08, 2025, 08:34 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 08, 2025, 10:14 PM UTC

    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.

  4. identified Jul 08, 2025, 11:45 PM UTC

    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.

  5. resolved Jul 09, 2025, 01:20 AM UTC

    Snowflake connectivity issues have been resolved and they have acknowledged that Explo's IPs were incorrectly blocked.

Read the full incident report →

Notice June 12, 2025 Degraded BigQuery Performance 7h 52m Customer Data Access, Customer Data Access

Started Jun 12, 2025, 06:16 PM UTC· resolved Jun 13, 2025, 02:08 AM UTC

  1. investigating Jun 12, 2025, 06:16 PM UTC

    We have noticed an issue with BigQuery data sources. We are investigating. Google has not updated their status page yet to declare an incident, but we are tracking potential issues on their end.

  2. identified Jun 12, 2025, 06:20 PM UTC

    Although there isn't a formal note on their status page yet, many folks are reporting issues with Google Cloud here: https://downdetector.com/status/google-cloud/ This is an issue with Google Cloud / BigQuery and not Explo.

  3. monitoring Jun 12, 2025, 07:04 PM UTC

    Google Cloud has now updated their status page: https://status.cloud.google.com/ We will continue to monitor. To reiterate, there are currently no service disruptions with the Explo platform and this is purely a Google Cloud issue.

  4. monitoring Jun 13, 2025, 02:08 AM UTC

    Google Cloud has now marked this as resolved.

  5. resolved Jun 13, 2025, 02:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 10, 2025 Explo system wide outage 1d 4h Explo Dashboards, Customer Data Access, Customer Data Access, Dashboard Embeds and 9 more

Started Jun 10, 2025, 07:44 AM UTC· resolved Jun 11, 2025, 12:08 PM UTC

  1. investigating Jun 10, 2025, 07:44 AM UTC

    We are currently investigating an issue affecting all Explo services. We suspect there is an issue with one of our providers Heroku

  2. investigating Jun 10, 2025, 07:45 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 10, 2025, 07:52 AM UTC

    We are actively monitoring this issue that Heroku is experiencing: https://status.salesforce.com/generalmessages/10001540

  4. identified Jun 10, 2025, 08:14 AM UTC

    We've identified the issue to be an issue with our cloud provider Heroku and are actively monitoring their status here: https://status.heroku.com/

  5. identified Jun 10, 2025, 01:00 PM UTC

    We are still actively monitoring this outage with our cloud provider, Heroku. Their latest update was that their parent company, Salesforce, has identified some network configuration issues on one of the servers within their Heroku environment, which could trigger this issue. They are monitoring closely and will update us when they get more information.

  6. identified Jun 10, 2025, 02:10 PM UTC

    Heroku services are slowly and intermittently coming back up. This will take some time to fully heal, but we are finally seeing some requests succeed again. We are unable to access any internal Heroku resources on our side (that we usually can log into), so we can't get any more information on our own. We verified this by consistently checking a wide range of requests and following their updates.

  7. identified Jun 10, 2025, 02:49 PM UTC

    We just received this hopeful update from Heroku: "We have restarted a subset of our Heroku instances. This has shown positive results for the impacted services. We are working to restart the rest of the Heroku instances to fully restore the services. We are continuing to validate and closely monitor the services."

  8. identified Jun 10, 2025, 04:28 PM UTC

    Latest note from Heroku: "We've restarted Heroku's internal platform apps and are actively monitoring to confirm whether the issue is resolved. However, errors are resurfacing." You can follow along here: https://status.salesforce.com/generalmessages/10001540 From the Explo side, we are simultaneously trying to move off of Heroku, however, we have some secrets (passwords / hidden keys for the service) that are stored in the Heroku product that we are unable to get access to. This is making it difficult to actually spin up the replacement service. We have some leads and ideas we are tracking to hopefully get this up and running.

  9. identified Jun 10, 2025, 07:42 PM UTC

    Here is the latest from Heroku: "We are actively developing the fix and working to determine a resolution timeline. Once the fix is complete, it will undergo testing in our pre-production environments to validate its effectiveness." Heroku and Salesforce are continuing to iterate on their fix, and we hope it will be available soon. Our engineering team continues to surge on moving the backend service from Heroku to AWS. With the restrictions we mentioned previously, there are clear roadblocks, but we feel optimistic about getting a backstop soon. This backstop will be independent of Heroku's fix they are working on.

  10. identified Jun 10, 2025, 07:54 PM UTC

    This is the latest from Heroku: "We are observing positive results in our initial testing on pre-production environments. We're continuing to test the fix before applying it to production environments and will provide a resolution timeline once determined." Taking this with a grain of salt, but sending it along for transparency.

  11. identified Jun 10, 2025, 09:00 PM UTC

    Update from Heroku: "We don't have additional information to share at this time. Our efforts remain focused on internal testing and validation as we continue to see incremental improvements. We will provide a resolution timeline as soon as possible, and we apologize for the continued trouble." Here are our updates. We are in the process of hydrating the AWS service's DB with a backup. Once that is up and a few other items, we will be very close to having the backstop in place. There will be restrictions to the backstop as we are optimizing for getting embeds working for end users and not a full blown replacement. More info to come. Thank you all so much for being patient and understanding.

  12. identified Jun 10, 2025, 10:05 PM UTC

    New update from Heroku: "The Heroku dashboard is now back online. Customers can now attempt to recycle their dynos on the dashboard. Specific instructions for recycling dynos will be shared shortly." We don't know exactly the implication of this yet and are testing on our side. Meanwhile the team is doing some final testing on the AWS service. We will update shortly based on what we learn from both points.

  13. identified Jun 10, 2025, 10:27 PM UTC

    A quick update. We are ready to cut over to the AWS service, we have instructions and context ready to go. However, we waited given Heroku's most recent update. With the most recent update, we attempted to reboot the nodes and then stopped them as they suggested. We are seeing nodes come back up and properly respond to requests now. Things should slowly get back to a stable state (based on the information we have). Heroku has not marked the incident as resolved, so we don't think we are in the full clear yet, but embedded dashboards and report builders should load again. Marking as degraded performance for now as we continue to monitor.

  14. identified Jun 10, 2025, 11:52 PM UTC

    Heroku has not indicated that services are fully back, but based on our logs and metrics, we are seeing the backend service to be healthy at this time. Our team continues to monitor closely, but services seem back to normal.

  15. resolved Jun 11, 2025, 12:08 PM UTC

    Heroku has indicated that services are fully back, so we are marking this issue as fully resolved. We will continue to closely monitor our backend service, and will reach out to customers in the coming days with an RCA and next steps

Read the full incident report →

Minor May 21, 2025 Degraded query performance in new connector infrastructure –

Started May 21, 2025, 05:27 PM UTC· resolved May 21, 2025, 05:27 PM UTC

  1. resolved May 21, 2025, 05:27 PM UTC

    We observed an issue where a new deploy caused our data connector to non-deterministically fail queries. We rolled back the deploy as soon as the alerts were detected and the issue was resolved

Read the full incident report →

Notice May 7, 2025 Data Connector Outage - 15 Min –

Started May 07, 2025, 07:00 PM UTC· resolved May 07, 2025, 07:00 PM UTC

  1. resolved May 07, 2025, 07:05 PM UTC

    This incident has been resolved

Read the full incident report →

Notice May 5, 2025 Partial Outage - Single Node Outage 1.5 Hours 4h

Started May 05, 2025, 12:15 PM UTC· resolved May 05, 2025, 04:15 PM UTC

  1. resolved May 08, 2025, 08:54 PM UTC

    One of the cluster's nodes went into a bad state and was unable to handle the execution of queries. Usually this self recovers as part of normal infrastructure rebooting, but this one did not and our team was paged and had to identify which node was impacted and restarted that particular one. 12:11pm -> triggered 1:54pm -> solved

Read the full incident report →

Major April 23, 2025 Report Builder Inaccessible 26m Explo Report Builder

Started Apr 23, 2025, 08:53 PM UTC· resolved Apr 23, 2025, 09:20 PM UTC

  1. identified Apr 23, 2025, 08:53 PM UTC

    We've identified an issue where viewing reports causes the page to crash - we have identified the fix and it should be out shortly

  2. resolved Apr 23, 2025, 09:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2025 Issues Sending Scheduled Report Builder Emails 1d 23h Exports: Email delivery

Started Feb 24, 2025, 04:00 PM UTC· resolved Feb 26, 2025, 03:00 PM UTC

  1. investigating Feb 28, 2025, 06:51 PM UTC

    We are investigating reports that scheduled report builder emails are not being received by end users

  2. resolved Feb 28, 2025, 06:52 PM UTC

    We have deployed the fix and are monitoring for further issues.

Read the full incident report →

Minor February 21, 2025 Intermittent Errors in Data Connector Infrastructure 20m Customer Data Access, Dashboard Embeds, Report Builder Embeds, Tabular Exports

Started Feb 21, 2025, 06:50 PM UTC· resolved Feb 21, 2025, 07:10 PM UTC

  1. investigating Feb 21, 2025, 07:30 PM UTC

    There are intermittent load errors while our system undergoes some abnormally high load

  2. resolved Feb 21, 2025, 07:30 PM UTC

    There are intermittent load errors while our system undergoes some abnormally high load

Read the full incident report →

Minor January 29, 2025 Inability to Create New Datasets 48m Explo Dashboards, Customer Data Access, Explo Report Builder

Started Jan 29, 2025, 01:40 PM UTC· resolved Jan 29, 2025, 02:29 PM UTC

  1. investigating Jan 29, 2025, 01:40 PM UTC

    Customers on the FIDO connector are unable to create new datasets, we are working on the fix and should have it resolved shortly.

  2. resolved Jan 29, 2025, 02:29 PM UTC

    A fix has been implemented and released.

Read the full incident report →

Critical January 24, 2025 Brief Outage during Database Migration –

Started Jan 24, 2025, 08:20 PM UTC· resolved Jan 24, 2025, 08:20 PM UTC

  1. resolved Jan 24, 2025, 08:20 PM UTC

    A database migration caused ten minutes of downtime while it ran. All Explo components were briefly inaccessible during this downtime.

Read the full incident report →

Major January 23, 2025 Issue with MySQL DB Connections –

Started Jan 23, 2025, 02:00 AM UTC· resolved Jan 23, 2025, 02:00 AM UTC

  1. resolved Jan 23, 2025, 08:01 PM UTC

    A regression was introduced that caused MySQL DB connections to fail on the legacy connector

Read the full incident report →