Same issue affecting my company. Jira Service Desk 7.11.2.

I'm not able to vote or comment on ATST-923. Looks like it's read-only to the public.

I can't seem to vote for this issue or the associated ATST issue but this is affecting my team.

Hello swh.tpe.ms! This bug ticket is currently closed as it belongs to the Atlassian Troubleshooting and Support Tools plugin, and it is currently being tracked under https://ecosystem.atlassian.net/browse/ATST-923. I suggest directing any feedback related to this bug to that request.

Best regards,
René Chiquete - Atlassian Support.

Using Jira 7.12.1 with application links to Confluence 6.3.1, Bitbucket 5.10.1 and Fisheye 4.6.0 we are getting the same warnings.
In a AO_..._HEALTH_CHECK_STATUS table we can see that the error logged is "One of your application links is reporting "Network error."

Looks like now this bug is being tracked under: https://ecosystem.atlassian.net/browse/ATST-923

Using Jira 7.12.1 and Confluence 6.11.2 will cause a lot of warnings inside atlassian-jira.log like 

2018-10-11 13:36:05,159 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3585f6eb-01d4-33ea-a14b-7d9069d00f95'
2018-10-11 13:36:05,206 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3099af41-80ad-3ea6-af7b-a96a7a7dabd0'
2018-10-11 13:36:05,237 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '15a64236-0e8f-3e67-b25a-72d35c7d44db'

This was after we update to the newest Version. We have no Problems like that before we update from 7.5.0 and Confluence 6.3.3.

we use Jira 7.11 , Confluence 6.11 and a generic Application

we are affected too.

I did not found anything in the logfiles

Jira 7.12 is also affected.

my post ( https://community.atlassian.com/t5/Jira-Software-questions/JIRA-Health-Check-returns-application-link-error-when-the/qaq-p/899602 ) is not marked as spam anymore. That means u should be able to vote for it now.

Same here with 7.11.0

@christopher.lewis911402510

i dont understand why, but yes the post is marked as spam... without any comments

Same here with Jira 7.11.2, Confluence 6.11.0 and ATST 1.13.0.

@Knut Luebke: I'd love to vote for the new bug report, but the link you posted isn't working ("It may have been deleted or marked as spam. ").

i reported here https://community.atlassian.com/t5/Jira-Software-questions/JIRA-Health-Check-returns-application-link-error-when-the/qaq-p/899602#M33493 the problem again, because the status of this issue here is already "resolved". It will be great if anybody who have still the same problem will vote in the new bug-report. Thx

Same issue with Jira 7.11.1 and Confluence 6.11.2.  Both apps running on the same server.

Started happening after upgrading Jira to 7.11.1 with Confluence on version 6.6.1.  Upgraded Confluence to 6.11.2 but the problem still occurs.

We have also updated (to 7.12.1) and we have that problem too.

started to receive these errors when I upgraded Jira from 7.8.1 to 7.12.0. We connect to Fisheye/Crucible on the same host, and Confluence on another host. Both links are reported in the error log.

Same here Jira 7.11.2 and Confluence 6.11.0

Still getting also this error with Jira 7.12 and Confluence 6.11

Getting this with Jira 7.11, Confluence 6.11

This bug is now tracked under ATST-853, as we no longer use jira.atlassian.com for Atlassian Troubleshooting & Support Tools issues.

Same problem. Non-profit organisation. Please provide a workaround. Does the option to disable this specific error notification exist? JIRA v7.7.0-m0003

@Starkey DevOps

I do not think it is JIRA-Confluence Issue . It rather seems to look like plugin issue that checks the links.

After seeing this problem after upgrading Jira to 7.5.3, I upgraded our Confluence instance to 6.5.2.  Still seeing the error occurring in JIRA.

This is occurring with JIRA 7.4.3 and Confluence 6.3.3 for us. We don't have any other JIRA applications that could be causing it and it won't disappear if we try to delete and reenable the link. It's a concern because we've had actual issues with our application links in the past and this false negative is concerning if that ever occurs again.

I got the same error after upgrading to JIRA 7.5.0

I can report the same between JIRA 7.4.1 and Confluence 5.7 and Confluence 6.2.1 saying " Multiple application links are reporting problems. "

I've noticed this behaviour with JIRA 7.4.2 & Confluence 6.1.1 - but I'm not sure if maybe Bamboo or Bitbucket application links are causing this.

Happening too with Jira 7.4.1 & Confluence 6.3.1