I’m still getting 80ms ping times, I’m half way across the globe from the very same servers you’re testing. 
EDIT: I forgot to add his recent post.
Like I said, find out where along the hop for your IP packet is causing you the most issue/adding most of that latency.
This is so simple that even I, as a stupid person, would know how to do.
You can use dig to time your DNS resolution if you think that the DNS resolution is the reason why it takes your IP packet so long for it to reach its destination.
I already ran mine, shown above.
“Query time: 2 msec”
“real 0m0.038s
user 0m0.005s
sys 0m0.021s”
Still < 80ms DNS resolution time according to dig if you think that’s the root cause of your issue.
. Go away dude. I’m HOPING that you’re like 15-16yrs old. If you’re an adult, seek psychiatric attention IMMEDIATELY before u end up on one of those serial killer shows. U have all the right character flaws to become one Mr Alpha Moron.
You’re the one who resurrected this.
It’s what I do. Put morons in their place.
…and also apparently, you also jerk off to guys because you have fetishes for me.
This is all I will have for u from here on out. Lmao
I know. You have nothing of significant, nothing of substance to offer.
You’ve provided two days’ worth of posts to back up the fact that you have nothing significant, nothing of substance to offer.
Whyyy…that’s mighty perspicacious of you.
The hilarious thing about this post is how u state that you searched high and wide for a reason for this payout. Meanwhile you were ON THE THREAD explaining it, but refuting everyone’s findings and acting like your 20MS times were something to call home about. Moron didn’t even know!!! I swear, u the best writers in the world couldn’t make this up. Reality is stranger than fiction. Especially when you throw people with mental issues in the mix.
The fact that you don’t seem to know how to run dig to test your DNS resolution times = you’re a fucking joke.
I don’t need DIG loser. I have a recursive resolver. Google it again. I know it’s advanced terminology, but try to understand it, before u keep digging yourself in a deeper hole. Any moron can run a dig command. My setup is more advanced than that. I wouldn’t expect u to understand moron. The fact that I’ve had to explain this like 4-5 times already, and the fact that u had to Google what a recursive resolver is tells me u don’t have a clue what you’re doing. U just copy and paste commands u see online. Moron.
Should I call u Copy and Paste man too? Let me dig up a character image for your second personality. Be right back!
“Any moron can run a dig command. My setup is more advanced than that”
Yes, and even GIVEN that, the data STILL shows that you’re wrong as my system resolved the DNS in < 80ms
AND my ping times are also less than 80ms.
In other words, tested both ways (DNS vs. the time it takes for the IP packet to travel to its destination) - BOTH show < 80ms.
Even someone as stupid as I am would know to run basic tests/diagnostics as a part of performing the root cause analysis to figure out where along the way, is causing the IP packet latency to increase, which results in a >80 ms ping time.
This is so basic and simple that even I, as a stupid person, can run these tests, and insodoing, it didn’t take much for me to be able to take screenshots of the evidence which shows that you’re wrong.
LOL…
Like I said, you already have the perfect picture: the cowardly lion from The Wizard of Oz.
It DEFINITELY suits you and is very much “on point”. 
You rig resolved in under 80MS AFTER they resolved their issues moron. BUT, u already have this detail, because your moronic post asking what the refund was for clearly shows two things:
-
Your rig was off the pool servers for an extended period of time, which was what that thread was about.
-
You’re such a moron that u didn’t even know that had happened 2 DAYS BEFORE.
YET, here u are. Still being the narcissistic moron that u have been since the very first post two days ago. BRAVO!!! 
No, they CLEARLY DIDN’T resolve their issues.
You’re on a roll in regards to how many times you can be wrong in a week.
If they had actually resolved their issues, then this CLEARLY wouldn’t have/couldn’t have been possible.
BWAHAHAHA…
And once again, Mr. Wrong is wrong - again.
BWAHAHAHA…
Mine is just fine. Separate issue. Mine is just fine and resolving in under 20MS. The upgrade to the infrastructure was completed 2 DAYS AGO. NICE TRY THO!!! Creative!! Keep it coming. U have turned into me and my coworkers psych project. We might use this for a psych paper.
EDIT: For evaluation purposes, we were curious as to what are your thoughts on the infrastructure upgrade that caused the outage in the first place. What are your thoughts on that? 
“Mine is just fine. Separate issue. Mine is just fine and resolving in under 20MS”
What did I fucking tell you?
LOL…LMAO…
You literally wrote, 2 days ago, August 24 at 4:07 PM
“Just check your net stats, you won’t see a ping under 80ms from ANY server at any given time, usually it’s 300-3,000ms.”
Which means that if they fixed it two days ago, you would have been seeing ping times in the 20ms mark like you are seeing now.
The presentation of my data to you first showed up 10 minutes after you had written quote:
“Just check your net stats, you won’t see a ping under 80ms from ANY server at any given time, usually it’s 300-3,000ms.”
Fast forward to now:
“The upgrade to the infrastructure was completed 2 DAYS AGO.”
Yet you were STILL bitching about this 2 days ago, so which is it?
Did they or did they NOT complete the infrastructure upgrade, 2 days ago, when you started bitching about it and I was already able to show you the data that proved that your statement was wrong?
Futhermore, if you look at the date/time stamps in the screenshot, this is from August 25, at approximately 21:40pm (according to the chart), which ISN’T two days ago Mr. Wrong.
Therefore; even if they had completed their upgrade 2 days ago, the problem that I have highlighted/shown ONCE AGAIN, comes from less than 18 hours ago as of this writing.
Therefore; if the upgrade had completed, then what I am showing shouldn’t have been possible, and yet, once again, the data flies in direct contradiction to your statement, Mr. Wrong.
LOL…LMAO…