The Site → Site Tools > lq1.dslreports.com sporadic pings during the day

lq1.dslreports.com sporadic pings during the day

Hi All,

I test my connection quite often and try to compare to historic data.
The way I see it, the move to the new server (liquidweb) should have no bearing since the tests are done from the same locations as before for "Line Quality".

I used to be an RCN customer who has migrated over to FiOS atleast for this year.
The very first day on FiOS pings to my ip from lq1.dslreports.com and lq2.dslreports.com dropped by a bit.

However, I've tried to understand what is causing sproadic pings from the lq1.dslreports.com site over the course of the day for the last two months on FiOS.
I never experienced these sporadic ups and down when I was on RCN.

Should I just assume that traffic patterns have changed from lq1.dslreports.com to my IP and that this is the norm for FiOS users?
lq2.dslreports.com is almost always consistently around 70-80ms pings.
lq1.dslreports.com at the lowest is about 39.6ms (from kansas to new york city) and at the worst it about 115ms or so on a horrible day.

My connection doesn't exhibit any usage issues to sites i normally visit.
gmail is about 4-5ms away
yahoo is about 20ms away
speedtest.net indicates the inerail test server pings at about 6-8ms

Another thing I've noticed is that certain verizon fios IP pools make my pings jump very high.
For instance, my current ip pool of 108.41.*.* is consistently lower in ICMP echp responses compared to the 70.*.*.* pool

Some weird behavior. However, I'm trying to understand this a little better. Is the lq1.dslreports.com proving to be sporadic for others as well?

The only thing that i expected to change (and i can confirm that it has changed) is that the tweak tester has made my results slightly more latent.
Before server move: tweak tester range was about 5ms to 10ms (pings to dslreports.com were about 7 or 8ms)
After server move: tweak tester range is between 30ms to 40ms (pings to dslreports.com are currently in the 30ms range).
--
"Look at me, I'm Dr. Zoidberg, homeowner."

those machines have not changed although I can't say what if anything is happening in the data centres they are in.
does smokeping show anything interesting?

Is there a reason why lq1.dslreports.com is hosting an apache server webpage.
lq2.dslreports.com doesn't have such a webpage.

Justin:
Are you guys cooking something up or is this some sort of a fluke?
Also, lq1.dslreports.com always evaluates to u15150124.onlinehome-server.com when trying to run ping or traceroute.

cchhat01
--
"Look at me, I'm Dr. Zoidberg, homeowner."

it's a 1 and 1 server
has a default apache install does it matter?

I suppose it probably isn't a dedicated server if it is turning out to be a different ANAME record. Maybe that's the cause of the server showing such a huge discrepancies in my line quality tests... anything coming from lq2.dslreports.com (which I suppose is hosted by megapath) is mostly flat-line pings (meaning that ping variations are very minimal) and constantly around 69-70ms most times of the day.

lq1.dslreports.com pings have varied quite drastically throughout the day. Just trying to figure out whether it's me OR me and other verizon fios folks around me OR simply the lq1.dslreports.com server (from a low of 44ms to a high of 105ms)

thats all... the fact that an apache server is installed there is meaningless to me (unless it is somehow causing the ups and downs in the pings)
--
"Look at me, I'm Dr. Zoidberg, homeowner."

it runs smokeping as well and mine is flat:
»/r3/smokeping.···888fc.NY

yeah it seems something is happening that I can't explain for verizon fios folks (maybe just for new yorkers i mean i really don't have other data to go by).
my smokeping wasn't flat like yours from lq1. lq2 is good. i did a line quality test to a router in india and even THAT is flat also (albeit at about 300+ms)

I'm starting another smokeping as we speak... for an extended period now that i have found an ip pool that i can stick with...
--
"Look at me, I'm Dr. Zoidberg, homeowner."

it doesn't absolve the data center hosting smokeping yet because their route to fios might be via a cheapie provider that is overloaded at certain times. In other words it is hard to say what the cause is when it is neither at "A" nor "B" but in between.

I couldn't have said it better myself...

»/r3/smokeping.···063d9066

Yep the route between lq1.dslreports.com and my ip has "rush-hour" based traffic. This could be peering related issues or a dog taking a proverbial poop at some point in the interconnects for all I know...
--
"Look at me, I'm Dr. Zoidberg, homeowner."