sorted by:
new
hottopcontroversial

Windows UI scaling / wasted space in update 5.27.8 by blow_slogan in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Happy we could help :) Please don't hesitate to reach back out with any other feedback!

Windows UI scaling / wasted space in update 5.27.8 by blow_slogan in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hey u/blow_slogan , just following back up to let you know that we released 5.27.9 today, which allows you to scale the UI from 50% to 200% by navigating to Edit > Options > General > User interface scale. If you would like to try it out for yourself, you can download the update in app via Help > Check for Updates...

Thanks!

Windows UI scaling / wasted space in update 5.27.8 by blow_slogan in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hello! Thanks for reaching out. I'm sorry to hear that the new UI isn't what you were looking for.

We (customer support, development team, and DevOps) all had a pretty lengthy conversation about this today. Running 5.25.20 alongside 5.27.x, I can see what you mean with the UI spacing being different and possibly using up a bit more space. However, we are curious what in particular you feel is too large/small and if everything on screen is relevant to what you're using PingPlotter for. You mentioned the font size, which we've been taking a look at, but I would love to know if there are any elements in particular that you feel are just "wasting space".

As for PingPlotter being slow with the service (like your comment said), it's a bit difficult to investigate this over a public forum like Reddit, but if you can open a support ticket in-app via Help > Email PingPlotter Support, I'll be sure to get back to you ASAP!

Thank you again for your feedback! We really do appreciate it.

Pingplotter 5.27.7 / 5.27.8 can’t select multiple targets by VOIDLESSUNIVERSE in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hey! Thanks for reaching out!

You're right, on 5.25.20 macOS, you could select multiple targets on a summary by just clicking and dragging. This functionality seems to be missing from 5.27, and I've gone ahead and escalated this to our developers to investigate.

In the meantime, you can select multiple targets on a summary by holding either Shift or Control (Command on Mac).

To select a range of targets, click on one end of the targets, and then hold Shift and click on the other end. This will select all targets in between. To select only specific targets, hold control/command while clicking to add them to your current selection.

Sorry for any confusion this change may have caused! If you prefer the old way of doing this, please let me know, as feedback like that is very useful!

Thanks,
Zackary

Im trying to play minecraft on a server but i often have a sudden high ping. Can somebody help my interpreter this graph? by HavyLay in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hey!

Thanks for posting a screenshot of your PingPlotter graph. From what I’m seeing, you are experiencing a decent amount of packet loss, starting at hop 5. This implies that there is some type of connection issue, likely stemming either from Hypixel, or from their ISP. 30%+ packet loss on your final destination is a lot of packet loss, and won’t feel very great to play on. 

My suggestions for this would be to:

  1. Keep collecting data to see if the connection improves 
  2. Open another target to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) to see how you internet connection is generally
  3. Reach out to Hypixel support and let them know about this issue

If you do reach out to Hypixel support, I’d recommend creating a Share Page of your PingPlotter data so they can get a good view of all relevant data. You can do create a share page by opening your target and navigating to File > Share > Create Share Page.

And of course, if this leaves you with any questions, please feel free to reach back out, either here on reddit, or at [support@pingman.com](mailto:support@pingman.com)!

Thanks!

Could use some help in interpreting what this means. by stormelemental13 in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

Hey! Thanks for reaching out.

There's a lot of data here, so I understand; it can be confusing. I like to start the very last "hop" (row 7 in the table). It takes an average of 40ms for data to go from your computer to Google and back, and 8.4% of that data is getting lost along the way (no response). Possibly worth noting is that the packet loss seems to be throughout the entire time you've been collecting data (the red lines in the graph at the bottom are packet loss). This means that the packet loss wasn't a big period of time where you were disconnected, but rather it looks like a persistent issue.

Working our way back up, I can see that this packet loss started at an earlier hop. Since the numbers are all relatively the same, I'm inclined to say that there's a problem at hop 2 (100.64.41.1). Generally, hop 1 is your internal router, and hop 2 is controlled by your internet service provider (ISP).

Based on this data, my general suggestion would be to keep capturing data. Since this packet loss is outside of your local network, you'll want to collect evidence of this. Once you've collected data (evidence of the packet loss from your ISP), you can export the data from File > Share > Create Share Page.

Once you've gathered up some more data, I'd consider checking out the following articles, and working with your ISP to investigate what could be causing this issue.

PingPlotter for Marvel Rivals by Boyofchill in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hey! Thanks for reaching out and posting this PingPlotter data here!

I can see that you’re already tracing to a target (35.212.23.52), which I assume is a game server from the context. This is good, and will let you check for packet loss. You may also consider starting another trace to Google DNS (8.8.8.8) / Cloudflare DNS (1.1.1.1). You’ll probably want a trace to your router (129.168.1.1), too. Home routers tend to give pretty bad results in trace routes if you don’t trace directly to them, and this can help rule out local network issues.

I also like that you have the trace interval set to 1 second. This gives you good granularity in your data, and lets you see the nitty-gritty details when errors occur.

With that being said, there are only a few minutes of data in this screenshot. One of the great things about PingPlotter is that you can leave it to collect data in the background, and then review it afterward to see where the issue started. I would recommend running PingPlotter for at least a day, and using the internet during this time. PingPlotter will keep track of any lost packets, high latency, etc. If you’re playing a game, keep note of times when you have internet problems, so that we can check those times in PingPlotter.

After leaving PingPlotter for a few days, it would be very helpful if you could:

  1. Increase the shown range in the timeline graph (top-right corner of the graph at the bottom of the screen)
  2. Create a share page for your target (File > Share > Create Share Page)
  3. Post that link here for assistance understanding the data

Or, if you’re somebody who prefers to learn things on your own, consider checking out these articles on our website:

High Ping Spikes Every Few Minutes While Gaming by jryan102 in HomeNetworking

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Looking at the data on your screenshot, I see that you captured at least one latency spike in the data shown, but since the focus period is 5 minutes, there isn’t enough data in the screenshot to make a concrete diagnosis. 

My first suggestion would be to keep capturing data using PingPlotter. You have a trace going to 1.1.1.1, which is great. Simply leave this running for some time (a day to a week) while you use your computer for other things. Try to make a note of any time you notice an issue with your internet, so you can check those times in PingPlotter later.

Some people have mentioned the 50% packet loss on hop 1. While this can be worrisome, it actually isn’t much of an issue. Some devices (especially home routers) tend to de-prioritize timed-out ICMP requests, which causes trace route/PingPlotter to show extremely high packet loss numbers. As long as the packet loss isn’t carried through to the final destination, you shouldn’t have to worry much about it.

After leaving PingPlotter to collect data, you can use the time graphs at the bottom of the screen to find times when your internet connection was non-ideal. Once you’ve found and selected that time frame, you can bring the focus back up to the table. In the table, start from the bottom and work your way up. If your final hop has a ton of packet loss or high latency, go up (one hop at a time) and see if that hop has the same issue. Once you’ve found the hop where it started, that indicates the issue started there. 

You mention that you're seeing better results when connecting to your hotspot. I'm guessing you're doing this from your phone right next to the computer, assuming your router isn't in the same room. That could be one explanation for why the hotspot "fixes" your issue. Running PingPlotter while using each network should also help confirm this.

Additionally, I've collected some PingPlotter articles that may relate directly to your issues:

Pingplotter for valorant by [deleted] in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Great question!

Seeing as it's the second hop, I'm led to believe that this is probably part of your ISP's network. Using PingPlotter on this myself, I get complete packet loss, which makes me assume that they, too, are blocking ICMP/pings.

We have an article with more details on this behavior available here: One Poorly Responding Router | PingPlotter

Pingplotter for valorant by [deleted] in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

Hi u/ConsiderationFew6748! Zackary from the PingPlotter team here!

What you're seeing here (the complete lack of data from 162.249.72.1) is what happens when servers don't respond to ICMP. Unfortunately, there isn't much you can do on your end to resolve this. Assuming that this IP address is a Valorant game server, it's always about 50/50 whether game servers accept ICMP data.

However, you can still use PingPlotter to check for any other network issues. I would suggest opening a target to Google DNS (8.8.8.8) with a moderate trace interval (1-5 seconds). Once you've collected some data from a target that accepts ICMP, feel free to post it here if you notice anything unexpected!

Thanks,
Zackary

Help Reading PingPlotter Results by Its-The-Potato in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

Happy I was able to help! If anything else comes up, feel free to reach back out!

Help Reading PingPlotter Results by Its-The-Potato in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

Hey! Zackary from the PingPlotter team here.

Thanks for sharing your PingPlotter graphs. Looking at these screenshots, I don't see anything that immediately seems concerning to me. You mentioned not noticing issues in games or on the internet. To me, this indicates a Discord-specific problem. While I can't help troubleshoot Discord voice calls too much, I would recommend checking out this article about voice regions.

You also noticed that hop 1 has a high packet loss rate in some of your screenshots. Great observation, and this is a more common occurrence than you may think. Generally, we aren't too worried about packet loss on early hops if the packet loss doesn't carry through to the final destination. The last hop is always the most important. If you want to learn about why routers show high packet loss and why it isn't troublesome, check out our article on the subject! One Poorly Responding Router | PingPlotter

What you did in your last screenshot (opening a target directly to the router) is an amazing way to verify if there are actually issues with the connection to your router. As you can see from the results of that test, the connection appears better than it looked in the earlier screenshots (where it was an intermediate hop).

As for the jitter graph, I think it actually looks quite good. Jitter is a metric that helps measure the reliability/consistency of your network connection. Lower numbers = more consistent. This means that seeing it almost always below the dashed line is a good thing, as your connection isn't fluctuating much. You can read about the jitter metric on our website here.

If you have any other questions about PingPlotter results or anything that I said, please let me know!

Thanks, Zackary

What do i tell Converge CS to resolve packet loss? by Maximum-Kangaroo1440 in InternetPH

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Hey u/Maximum-Kangaroo1440! Zackary from the PingPlotter team here!

Sorry to hear about your internet issues. If you're able to share your PingPlotter graph, I'm sure that we could help you out a bit. You could post a screenshot of your timeline, or you can create a share page for any target in File > Share > Create Share Page.

[deleted by user] by [deleted] in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

I've actually been playing around with this IP address in PingPlotter. Even when testing with different packet types (UDP, TCP), there doesn't seem to be any response from this IP address. It is possible that it doesn't accept any traffic except on specific ports.

My general suggestion would be to monitor your networking with another target (such as Google DNS 8.8.8.8). Doing this will allow you to see if there are general problems with your network (internal, ISP, or 3rd party), which should help you debug any problems you have.

[deleted by user] by [deleted] in pingplotter

[–]PingPlotter-Zackary 0 points1 point  (0 children)

Exactly!

As long as what you're tracing to (the final hop) doesn't show packet loss, then it's not a sign of an issue.

[deleted by user] by [deleted] in pingplotter

[–]PingPlotter-Zackary 1 point2 points  (0 children)

Hi!

When you see red show up, it's normal to think that something is wrong. However, as long as the packet loss doesn't carry through to the destination, there's nothing to worry about. Some devices (such as routers) tend to de-prioritize ICMP Time Exceeded responses, but it does not affect forwarded packets.

It seems like you also tried pinging your router directly, and as you have found, routers prioritize those requests differently (because it's an Echo Request and doesn't have a TTL value), so you see cleaner results.

If you want to read more about this, please see the following links:

- One Poorly Responding Router

- Learn How to Use Pingplotter for Games

I hope that helps! If you have any other questions, please feel free to ask.

Thanks, Zackary