Tracify Outage History

There were 3 Tracify outages since March 12, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tracify.ai

Minor March 31, 2026

Increased latencies for various services

Detected by Pingoru: Mar 31, 2026, 05:50 PM UTC
Resolved: Mar 31, 2026, 05:50 PM UTC
Duration: —

Affected: ChiefDashboardChrome-PluginTracify-API

Timeline · 3 updates

investigating Mar 31, 2026, 05:37 PM UTC

Status: Investigating 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. Affected components Chrome-Plugin (Degraded performance) Chief (Degraded performance) Dashboard (Degraded performance) Tracify-API (Degraded performance)
monitoring Mar 31, 2026, 05:40 PM UTC

Status: Monitoring 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. Affected components Dashboard (Degraded performance) Tracify-API (Degraded performance) Chrome-Plugin (Degraded performance) Chief (Degraded performance)
resolved Mar 31, 2026, 05:50 PM UTC

Status: Resolved Response times seem to be better now. We still monitor the situation. Affected components Tracify-API (Operational) Chrome-Plugin (Operational) Chief (Operational) Dashboard (Operational)

Read the full incident report →

Minor March 25, 2026

Potential ingress problem

Detected by Pingoru: Mar 25, 2026, 07:40 PM UTC
Resolved: Mar 25, 2026, 07:40 PM UTC
Duration: —

Affected: Gateway

Timeline · 5 updates

investigating Mar 25, 2026, 01:48 PM UTC

Status: Investigating 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. Affected components Gateway (Degraded performance)
identified Mar 25, 2026, 02:07 PM UTC

Status: Identified 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. Affected components Gateway (Degraded performance)
monitoring Mar 25, 2026, 02:08 PM UTC

Status: Monitoring 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. Affected components Gateway (Degraded performance)
resolved Mar 25, 2026, 02:15 PM UTC

Status: Resolved 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. Affected components Gateway (Operational)
resolved Mar 25, 2026, 07:40 PM UTC

Status: Resolved 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 Affected components Gateway (Operational)

Read the full incident report →

Minor March 13, 2026

Delayed Data Processing (Analytics Dashboards)

Detected by Pingoru: Mar 13, 2026, 10:52 AM UTC
Resolved: Mar 13, 2026, 10:52 AM UTC
Duration: —

Affected: Data Pipelines

Timeline · 7 updates

investigating Mar 12, 2026, 02:25 PM UTC

Status: Investigating 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. Affected components Data Pipelines (Degraded performance)
identified Mar 12, 2026, 02:57 PM UTC

Status: Identified We have identified the underlying problem and are now working on a fix. We will provide another update once the fix is rolled out. Affected components Data Pipelines (Degraded performance)
investigating Mar 12, 2026, 03:56 PM UTC

Status: Investigating 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. Affected components Data Pipelines (Degraded performance)
monitoring Mar 12, 2026, 05:49 PM UTC

Status: Monitoring 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. Affected components Data Pipelines (Degraded performance)
resolved Mar 12, 2026, 06:48 PM UTC

Status: Resolved 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. Affected components Data Pipelines (Operational)
resolved Mar 12, 2026, 08:38 PM UTC

Status: Resolved 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. Affected components Data Pipelines (Operational)
resolved Mar 13, 2026, 10:52 AM UTC

Status: Resolved 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. Affected components Data Pipelines (Operational)

Read the full incident report →

Looking to track Tracify downtime and outages?

Pingoru polls Tracify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Tracify reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Tracify alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Tracify for free

5 free monitors · No credit card required