Can you please share the dashboard URL where this is incorrect? You can DM me if you prefer.

@silly-train-16715 thank you for reporting. Not conclusive yet, but this looks like it could be due to padding packets not getting accounted properly. Browsers use padding packets to probe for bandwidth. In this case, it looks like maybe a bunch of padding packets got lost and that did not get accounted properly causing that out of range number. We will dig into this more and address it. Please let us know if you see more instances of it.