![]() ![]() ![]() |
|
It's looking like the bad route is probably severely congested as well. For the couple of nights I've had SmokePing running, I've noticed that packet loss drops off a cliff overnight, when there's likely far less traffic on the pipe.
Today's the worst it's been so far. I've been troubleshooting some unrelated issues, and stumbling across places where people have been posting imgur links/images. It's frequently outright failing to load.
I'm seeing upwards of 90% packet loss on some of these hops. It's grim. Given I also work from home, stuff like this can sometimes materially slow me down. I was hoping it would get better instead of worse.
Kodiack:
Today's the worst it's been so far. I've been troubleshooting some unrelated issues, and stumbling across places where people have been posting imgur links/images. It's frequently outright failing to load.
Try now.
My SmokePing to imgur.com has suddenly started looking happier, and the MTR is looking a bit better (still some loss on that second hop, but unsure whether that's inherently problematic). Guessing this was partially your work, @sounddude. I'm glad to see it!
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. router.lan 0.0% 22 0.3 0.3 0.2 0.3 0.0
2. v1.akmod-bng1.tranzpeer.net 9.1% 22 2.6 2.7 2.1 3.4 0.4
3. 10.101.0.158 0.0% 22 2.9 4.0 2.8 18.5 3.3
4. 199.232.196.193 0.0% 21 141.0 140.5 140.1 141.0 0.3
NOC have come back to me and the issue with Imgur.com is resolved now. However, the issue with Cloudflare Relay is still there (32% packet loss).
Everything I was having issues with works for me now, I'm seeing no loss. Are you able to share a little detail on what the problem was? Thanks.
boosacnoodle:
NOC have come back to me and the issue with Imgur.com is resolved now. However, the issue with Cloudflare Relay is still there (32% packet loss).
What IP are you testing to?
Sounddude:
boosacnoodle:
NOC have come back to me and the issue with Imgur.com is resolved now. However, the issue with Cloudflare Relay is still there (32% packet loss).
What IP are you testing to?
104.21.16.1
A more complete set based on post #3333086 might be
dig +short A ping.mcgrath.nz @202.180.64.10
104.21.96.1
104.21.64.1
104.21.48.1
104.21.112.1
104.21.80.1
104.21.16.1
104.21.32.1
I suppose these would be one set of IPv4 addresses used to access ephemeral services exposed by Cloudflares reverse tunnel.
Edit: as above 104.21.16.1 might be the last one from that set still needing to whitelist.
boosacnoodle:
104.21.16.1
Will get that one sorted too
Sounddude:
Will get that one sorted too
This is another one I was watching. It wasn't too bad for me, but it did have some packet loss and a wonky route. It looks like it got resolved within the past couple of minutes. :)
What was causing this route?
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy:
What was causing this route?
I'm curious to know as well, but in my case it was also going through 101.98.5.93 before things went sour. I wasn't dropping packets at that IP for that route, but shortly after.
|
![]() ![]() ![]() |