I've noticed this pattern is existing code that polled discovery data to determine if an instance is up.  I can only assume that there was some issue with the application name associated with the instance in the discovery service somehow was different from the application name the client thinks it belongs to.  If that is the case then this seems like a bug somewhere else in eureka.