easy-accordion-free domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114zoho-flow domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114At 3:40 p.m. EST on March 6, 2024, Zscaler Digital Experience (ZDX) saw a substantial, unexpected drop in the ZDX score for LinkedIn services around the globe. Upon analysis, we noticed HTTP 503 errors highlighting a LinkedIn outage, with the ZDX heatmap clearly detailing the impact at a global scale.<\/p>\n
ZDX dashboard indicating widespread LinkedIn outage<\/p>\n
ZDX enables customers to proactively identify and quickly isolate service issues, giving IT teams confidence in the root cause, reducing mean time to resolve (MTTR) and first response time (MTTD).<\/p>\n
ZDX dashboard showing LinkedIn global issues<\/p>\n
ZDX Score highlights LinkedIn outageVisible on the ZDX admin portal dashboard, the ZDX Score represents all users in an organization across all applications, locations, and cities on a scale of 0 to 100, with the low end indicating a poor user experience. Depending on the time period and filters selected in the dashboard, the score will adjust accordingly.<\/p>\n
The dashboard shows that the ZDX Score for the LinkedIn probes dropped to ZERO during the outage window of approximately 1 hour. From within ZDX, service desk teams can easily see that the service degradation isn\u2019t limited to a single location or user and quickly begin analyzing the root cause.<\/p>\n
ZDX Score indicating LinkedIn outage and recovery (times in EST)<\/p>\n
Also in the ZDX dashboard, \u201cWeb Probe Metrics\u201d highlight the user impact of reaching LinkedIn applications across a timeline with response times. In this case, the server responded with 503 errors, indicating the server was not ready to handle requests.<\/p>\n
ZDX Web Probe Metrics indicating 503 errors (times in EST)<\/p>\n
ZDX can quickly identify the root cause of user experience issues with its new AI-powered root cause analysis capability. This spares IT teams the labor of sifting through fragmented data and troubleshooting, thereby accelerating resolution and keeping employees productive.<\/p>\n
With a simple click in the ZDX dashboard, you can analyze a score, and ZDX will provide insight into potential issues. As you can see, in the case of this LinkedIn outage, ZDX highlights that the application is impacted while the network itself is fine.<\/p>\n
ZDX AI-powered root cause analysis indicates the reason for the outage<\/p>\n
When there\u2019s an application outage, many IT teams turn to the network as the root cause. However, as you can see above, ZDX AI-powered root cause analysis verified that the network transport wasn\u2019t the issue; it was actually at the application level. You can verify this by looking at the CloudPath metrics from the user to the destination.<\/p>\n
ZDX CloudPath showing full end-to-end data path<\/p>\n
ZDX CloudPath detailed hops between the nodes<\/p>\n
With AI-powered analysis and dynamic alerts, IT teams can quickly compare optimal vs. degraded user experiences and set intelligent alerts based on deviations in observed metrics. ZDX allows you to compare two points in time to understand the differences between them. This function determines a good vs. poor user experience, visually highlighting the differences between application, network, and device metrics.<\/p>\n
The end user comparison during the LinkedIn outage vs. a known good score indicates the ZDX Score difference, highlighting the unexpected performance drop for the end user.<\/p>\n
ZDX comparison mode identifies the change in user experience<\/p>\n
According to the LinkedIn status page, the outage was reported at 12:50 PST until 14:05 PST, which correlates to the ZDX data above. However, LinkedIn services started to recover pretty quickly, by 13:40 PST, and LinkedIn reported the issue resolved by 14:05 PST. <\/p>\n
Source: LinkedIn<\/p>\n
With ZDX alerting, our customers were proactively notified about end user problems, and incidents were opened automatically with our service desk integration (e.g., ServiceNow) long before users started to report it. From a single dashboard, customers were able to quickly identify this as a LinkedIn issue, not an internal network outage, saving precious IT time.<\/p>\n
Zscaler Digital Experience successfully detected a LinkedIn outage along with its root cause, giving our customers the confidence that it was not a single location, their networks, or devices, averting critical impact to their business.<\/p>\n
Try Zscaler Digital Experience today<\/p>\n
ZDX helps IT teams monitor digital experiences from the end user perspective to optimize performance and rapidly fix offending application, network, and device issues. To see how ZDX can help your organization, please contact us.\u00a0\u00a0<\/p>\n
\u200b<\/p>\n
At 3:40 p.m. EST on March 6, 2024, Zscaler Digital Experience (ZDX<\/a>) saw a substantial, unexpected drop in the\u00a0ZDX score<\/a> for LinkedIn services around the globe. Upon analysis, we noticed HTTP 503 errors highlighting a LinkedIn outage, with the ZDX heatmap clearly detailing the impact at a global scale.<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX dashboard indicating widespread LinkedIn outage<\/em><\/p>\n \u00a0<\/p>\n ZDX enables customers to proactively identify and quickly isolate service issues, giving IT teams confidence in the root cause, reducing mean time to resolve (MTTR) and first response time (MTTD).<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX dashboard showing LinkedIn global issues<\/em><\/p>\n Visible on the ZDX admin portal dashboard, the ZDX Score represents all users in an organization across all applications, locations, and cities on a scale of 0 to 100, with the low end indicating a poor user experience. Depending on the time period and filters selected in the dashboard, the score will adjust accordingly.<\/p>\n \u00a0<\/p>\n The dashboard shows that the ZDX Score for the LinkedIn probes dropped to\u00a0ZERO\u00a0<\/strong>during the outage window of approximately 1 hour. From within ZDX, service desk teams can easily see that the service degradation isn\u2019t limited to a single location or user and quickly begin analyzing the root cause.<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX Score indicating LinkedIn outage and recovery (times in EST)<\/em><\/p>\n \u00a0<\/p>\n Also in the ZDX dashboard, \u201cWeb Probe Metrics\u201d highlight the user impact of reaching LinkedIn applications across a timeline with response times. In this case, the server responded with 503 errors, indicating the server was not ready to handle requests.<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX Web Probe Metrics indicating 503 errors (times in EST)<\/em><\/p>\n \u00a0<\/p>\n ZDX can quickly identify the root cause of user experience issues with its new\u00a0AI-powered root cause analysis<\/a> capability. This spares IT teams the labor of sifting through fragmented data and troubleshooting, thereby accelerating resolution and keeping employees productive.<\/p>\n \u00a0<\/p>\n With a simple click in the ZDX dashboard, you can analyze a score, and ZDX will provide insight into potential issues. As you can see, in the case of this LinkedIn outage, ZDX highlights that the application is impacted while the network itself is fine.<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX AI-powered root cause analysis indicates the reason for the outage<\/em><\/p>\n \u00a0<\/p>\n When there\u2019s an application outage, many IT teams turn to the network as the root cause. However, as you can see above, ZDX AI-powered root cause analysis verified that the network transport wasn\u2019t the issue; it was actually at the application level. You can verify this by looking at the CloudPath metrics from the user to the destination.<\/p>\n \u00a0<\/p>\n \n<\/p> ZDX CloudPath showing full end-to-end data path<\/em><\/p>\n \u00a0<\/p>\n \n<\/p> ZDX CloudPath detailed hops between the nodes<\/em><\/p>\n \u00a0<\/p>\n With AI-powered analysis and dynamic alerts, IT teams can quickly compare optimal vs. degraded user experiences and set intelligent alerts based on deviations in observed metrics. ZDX allows you to compare two points in time to understand the differences between them. This function determines a good vs. poor user experience, visually highlighting the differences between application, network, and device metrics.<\/p>\n \u00a0<\/p>\n The end user comparison during the LinkedIn outage vs. a known good score indicates the ZDX Score difference, highlighting the unexpected performance drop for the end user.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n ZDX comparison mode identifies the change in user experience<\/em><\/p>\n \u00a0<\/p>\n According to the LinkedIn status page, the outage was reported at 12:50 PST until 14:05 PST, which correlates to the ZDX data above. However, LinkedIn services started to recover pretty quickly, by 13:40 PST, and LinkedIn reported the issue resolved by 14:05 PST.\u00a0<\/p>\n \u00a0<\/p>\n \n<\/p>ZDX Score highlights LinkedIn outage<\/h3>\n