It's likely a cached leftover web resource that should naturally rotate out eventually. Depends on access logs, a lot could be guessed based on the surrounding traffic for the user but not much without it. Could be cached either client side or server side so yeah, depends a lot.
Only the vendor will know for certain if and what makes those calls and confirm the caching nature or whether it could be some other incorrectly de-registered module when the app is being uninstalled (though other than web resources I can't really think of anything that could persist on the system and inject http requests).
Generally I would expect those requests to phase out but if you are really piqued by it then access logs would be the place to start imo to get a better sense of where it's coming from.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.