Tracify Outage History

Tracify is up right now

Pingoru has recorded 11 incidents for Tracify: 11 in the last 12 months and 2 in the last 90 days.

Source: status.tracify.ai

11incidents recorded
11last 12 months
2last 90 days
15 daystypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Tracify 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 20260326 of 720 (45%)
May 202600 of 744 (0%)
June 202614 of 720 (1%)
July 2026114 of 744 (2%)
August 202600 of 744 (0%)
September 202613 of 720 (0%)
October 202611 of 744 (0%)
November 202600 of 110 (0%)

Incidents, newest first

Critical October 23, 2026 Shopify System 1h 16m Integrations (Shopify), Frontend (Dashboard)

Started Oct 23, 2026, 10:42 AM UTC· resolved Oct 23, 2026, 11:59 AM UTC

  1. identified Oct 23, 2026, 10:42 AM UTC

    We have identified a problem with our event ingestion for shopify events and are working on a resolution. Parts of our system like PnL and event ingestion for shopify stores is degraded.

  2. monitoring Oct 23, 2026, 11:41 AM UTC

    The affected components have been patched and are now monitoring the system to make sure everything works as expected. We will provide an update once we can confirm the fix is effective.

  3. resolved Oct 23, 2026, 11:59 AM UTC

    We confirmed that the fix resolved the problem. Apologies for the inconvenience.

Read the full incident report →

Minor September 17, 2026 API Degraded Status 2h 57m Backend (Chief), Integrations (Shopify), Integrations (Ad connector), Backend (Data Pipelines) and 2 more

Started Sep 17, 2026, 10:19 AM UTC· resolved Sep 17, 2026, 01:16 PM UTC

  1. monitoring Sep 17, 2026, 10:19 AM UTC

    We confirmed a problem with our system and identified the likely cause as ongoing incident with a core third party cloud service provider. We are monitoring our systems and will provide an update soon.

  2. resolved Sep 17, 2026, 01:16 PM UTC

    The underlying issue has been resolved and our services are back to normal.

Read the full incident report →

Major July 27, 2026 Missing ad metrics data 14h 21m Integrations (Ad connector), Frontend (Dashboard), Frontend (Chrome-Plugin), Backend (Tracify-API)

Started Jul 27, 2026, 03:23 PM UTC· resolved Jul 28, 2026, 05:45 AM UTC

  1. investigating Jul 27, 2026, 03:23 PM UTC

    We confirmed a problem with our ad metric system and are currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  2. resolved Jul 28, 2026, 05:45 AM UTC

    We confirmed that our fix resolved the problem. Apologies for the inconvenience.

Read the full incident report →

Major June 2, 2026 Data Pipeline Processing Problem 4h 8m Backend (Data Pipelines)

Started Jun 02, 2026, 09:27 AM UTC· resolved Jun 02, 2026, 01:36 PM UTC

  1. investigating Jun 02, 2026, 09:27 AM UTC

    We confirmed a problem with our system affecting data pipeline processing for a small number of clients and are currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  2. identified Jun 02, 2026, 09:57 AM UTC

    We confirmed a problem with our system (internal database) and our service partner is currently implementing an upgrade. We will provide an update once we confirm the incident is resolved.

  3. monitoring Jun 02, 2026, 10:18 AM UTC

    Our service partner has applied a patch to the affected components and is now monitoring the system to make sure everything works as expected. We will provide an update once we can confirm the fix is effective.

  4. resolved Jun 02, 2026, 01:36 PM UTC

    Our service partner confirmed that the problem is resolved. We can see that the data pipeline is working as expected, again. We still monitor the stats. Apologies for the inconvenience.

Read the full incident report →

Minor March 31, 2026 Increased latencies for various services 19d 7h Backend (Chief), Frontend (Dashboard), Frontend (Chrome-Plugin), Backend (Tracify-API)

Started Mar 31, 2026, 02:00 PM UTC· resolved Apr 19, 2026, 09:59 PM UTC

  1. investigating Mar 31, 2026, 05:37 PM UTC

    We confirmed a problem with our system and are currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  2. monitoring Mar 31, 2026, 05:40 PM UTC

    Our cloud provider has identified an issue with a networking component: https://exoscalestatus.com/incidents/229495 of his infrastructure and has informed us that it is resolved. We are monitoring the situation.

  3. resolved Mar 31, 2026, 05:50 PM UTC

    Response times seem to be better now. We still monitor the situation.

Read the full incident report →

Minor March 25, 2026 Potential ingress problem 25d 2h

Started Mar 25, 2026, 07:40 PM UTC· resolved Apr 19, 2026, 09:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 25, 2026 Potential ingress problem 27m Backend (Gateway)

Started Mar 25, 2026, 01:48 PM UTC· resolved Mar 25, 2026, 02:15 PM UTC

  1. investigating Mar 25, 2026, 01:48 PM UTC

    We confirmed a problem with our system and are currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  2. identified Mar 25, 2026, 02:07 PM UTC

    We have identified a problem with one of our ingress clusters and are now trying to re-route the traffic. We will provide another update once the fix is rolled out.

  3. monitoring Mar 25, 2026, 02:08 PM UTC

    We have successfully deployed the new ingress cluster and are now monitoring the system to make sure everything works as expected. We will provide an update once we can confirm our fix is effective.

  4. resolved Mar 25, 2026, 02:15 PM UTC

    We confirmed that our fix resolved the problem. Apologies for the inconvenience. We will run some additional investigation to find out how we can prevent the ingress problem in the future.

  5. resolved Mar 25, 2026, 07:40 PM UTC

    Our cloud provider confirmed issues on their end: further details can be found on [Network] Increased internet network latencies and packet loss: https://exoscalestatus.com/incidents/228561

Read the full incident report →

Minor March 13, 2026 Delayed Data Processing (Analytics Dashboards) 37d 11h

Started Mar 13, 2026, 10:52 AM UTC· resolved Apr 19, 2026, 09:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 12, 2026 Delayed Data Processing (Analytics Dashboards) 4h 22m Backend (Data Pipelines)

Started Mar 12, 2026, 02:25 PM UTC· resolved Mar 12, 2026, 06:48 PM UTC

  1. investigating Mar 12, 2026, 02:25 PM UTC

    We are currently investigating an issue with one of our database clusters that is causing a delay in data processing. As a result, some customers may notice that their real-time analytics dashboards are showing "stale" data or a processing lag of approximately 20–30 minutes.

  2. identified Mar 12, 2026, 02:57 PM UTC

    We have identified the underlying problem and are now working on a fix. We will provide another update once the fix is rolled out.

  3. investigating Mar 12, 2026, 03:56 PM UTC

    We confirmed a problem with our system (internal database) and our service partner is currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  4. monitoring Mar 12, 2026, 05:49 PM UTC

    Our partner for the underlying database informed us that they performed a manual recovery operation, which shows good system metrics. They are monitoring the situation. We hope the situation can be resolved soon.

  5. resolved Mar 12, 2026, 06:48 PM UTC

    The fix applied by our service partner seems to be effective, as the backlog is declining and already gone for most, except for one client. We will still keep monitoring the situation and post another update.

  6. resolved Mar 12, 2026, 08:38 PM UTC

    We can confirm the backlog for all clients is back to normal. There is still an upgrade process running in the background, but at the moment, it has no client impact. The service provider and the team are monitoring the situation.

  7. resolved Mar 13, 2026, 10:52 AM UTC

    Our service provider informed us that the database is back to its original state and is performing as expected. We are seeing that all is working as expected.

Read the full incident report →

Minor February 2, 2026 Errors loading reporting data 76d 11h

Started Feb 02, 2026, 10:16 AM UTC· resolved Apr 19, 2026, 09:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical February 2, 2026 Errors loading reporting data 34m Frontend (Dashboard), Frontend (Chrome-Plugin)

Started Feb 02, 2026, 09:42 AM UTC· resolved Feb 02, 2026, 10:16 AM UTC

  1. investigating Feb 02, 2026, 09:42 AM UTC

    We confirmed a problem with our system and are currently investigating its root cause. We will provide an update once we have identified the underlying problem.

  2. monitoring Feb 02, 2026, 09:58 AM UTC

    Issue identified with upstream data provider. Systems appear to be operational again, but waiting on full confirmation.

  3. resolved Feb 02, 2026, 10:16 AM UTC

    Upstream provider has confirmed incident should now be resolved. We're no longer experiencing errors in database connectivity.

Read the full incident report →