I am experiencing high levels packet loss in my route to the closest CF server, in Dallas, Texas, USA. Unfortunately it has been ongoing for around a month and did get better for a few days after Dallas had scheduled maintenance.
Unfortunately I believe I have finally exhausted all the steps I can take. On one website I have control over that the issue presented itself on, I de-orange clouded and received no packet loss.
At speed cloudflare com I get a persistent 10 - 30 percent packet loss as it connects to the Dallas datacenter.
I have confirmed this is only Cloudflare websites. I saw nowhere else I could report this.
I’m in Gulfport, MS and getting routed to DFW/Dallas CF servers and I’m getting average 13% packet loss from pings. From the CF speedtest it’s higher at like 18-25%.
Running ping test from a vpn to route it away gives me zero loss. I’m at a loss of what to do as well, it’s only Cloudflare websites and servers.
I’m in D’Iberville, MS and I’ve been having the same problem since late August. It only happens during specific hours of the day, and I get similar double-digit packet loss during those hours. This causes Cloudflare sites to become near unusable because of how badly their performance is affected.
I have heard that others in the area are experiencing similar, so this is a widespread issue. I don’t understand why this isn’t being addressed.
East Texas here routed through Dallas. Anything Cloudflare related after 2PM is between a 15-20% packet loss over a 5-minute span. Makes all CF sites unusable. Below is to the Shopify Admin portal.
I ran the Cloudflare speed test a few times during the hours the problem occurs, below is a sceenshot of just one of the results. It connects to Dallas each time.
@itsme: Seems like you left out a lot of traceroute information, which is most often going to do much more harm than it will do good. Can you share what AS number you are coming from?
@benelliottm93 & @robmail87: Could you please share a traceroute (e.g. mtr, WinMTR, PingPlotter, …), and what AS number you are coming from?
https://bgp.tools/
→ The AS number shown under “You are connecting from” like this: “Cloudflare, Inc. (AS13335)”
https://bgp.he.net/
→ The AS number shown like this: “Your ISP is AS13335 (Cloudflare, Inc.)”
This information (especially the AS number) would be essential for Cloudflare (and/or any other network) in order to be able to dig further in to such issues, such as for example attempting to find an alternative path that may cause less packet loss (if technically possible).
I don’t know what happened tonight, but things have improved dramatically. I ran traceroutes and the CF speed test a few times in the past few hours, and so far I haven’t seen any packet loss coming from Cloudflare addresses. The speeds from the CF speed test, while not perfect, are now much much better.
The only packet loss I do get are from the Level 3 addresses that very rarely pop up among the Cloudflare addresses on a traceroute. They are from Dallas too, so there’s probably a larger problem happening over there. Below is a traceroute I ran for a minute where I was able to catch a couple of Level 3 addresses. “No response from host” seems to be a common occurrence when they appear.
