This is a known issue, we’re keeping an eye on it internally.
Good to know, thanks for the updated info.