[X] My Assistant

I'm currently using HV as a guinea pig to try out Cloudflare. If you notice any changes in how HV performs, for better or worse, let me know. It will take up to 24 hours for the name servers to be updated, you can tell that they have updated for you if the IPs no longer resolve to 94.100.y.z.

If you can be arsed, also let me know how it performs with HTTPS.

105-106 ms ping
No noticeable difference between HTTP and HTTPS.

105-106 ms ping
No noticeable difference between HTTP and HTTPS.

And that's to a Cloudflare frontend (i.e. not 94.100.something)? I would expect the frontend ping to be lower than that for most people, but I guess that depends on your connection and ISP.

94.100.24.93

Avg ms consistently 107

Pathping:
2 206.80.253.242
3 xe-1-2-1-0.ipr02.totftds.distributel.net [206.80.255.54]
4 ge-2-0-2-970.ipr01.totftds.distributel.net [206.80.255.58]
5 xe-2-2-0-0.ipr01.totftds.distributel.net [206.80.255.52]
6 ae2.cr1-tor1.ip4.gtt.net [69.31.143.189]
7 xe-7-1-2.cr8-nyc3.ip4.gtt.net [89.149.130.149]
8 as2914.nyc34.ip4.gtt.net [199.229.229.190]
9 ae-2.r25.nycmny01.us.bb.gin.ntt.net [129.250.3.97]
10 ae-9.r22.asbnva02.us.bb.gin.ntt.net [129.250.2.149]
11 ae-0.r23.asbnva02.us.bb.gin.ntt.net [129.250.3.85]
12 ae-2.r25.amstnl02.nl.bb.gin.ntt.net [129.250.6.163]
13 ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.159]
14 ae-0.swiftway.amstnl02.nl.bb.gin.ntt.net [81.20.64.62]
15 251.17.100.94.static.swiftway.net [94.100.17.251]
16 93.24.100.94.static.swiftnoc.com [94.100.24.93]

This post has been edited by Maximum_Joe: Feb 19 2017, 22:04

That's still the old one, let me know if a day or so when your nameserver has updated. (Or do nslookup hentaiverse.org carl.ns.cloudflare.com to get the new one.)

Hmm, I did a DNS flush beforehand so it's not propagating for me yet. Will update tomorrow.

This post has been edited by Maximum_Joe: Feb 19 2017, 22:05

Hmm, I did a DNS flush beforehand so it's not propagating for me yet. Will update tomorrow.

Nameserver propagation is slower than normal DNS propagation, one full day is usual and it could take longer.

Hi, i had gathered some data before (like 2 weeks ago), and now since the ip updated.
Hid three hops (the same IPs) in both tracerts.
Italy here, btw.
Seems slightly faster than before, in real use.
Tell me if any of this is useful

Here is it:

OLD DATA:

Microsoft Windows [Versione 6.1.7601]
Copyright © 2009 Microsoft Corporation. Tutti i diritti riservati.

C:\Users\Administrator>ping -n 20 hentaiverse.org

Esecuzione di Ping hentaiverse.org [94.100.24.92] con 32 byte di dati:
Risposta da 94.100.24.92: byte=32 durata=275ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=142ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=330ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=119ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=325ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=105ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=324ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=121ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=474ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=366ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=318ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=480ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=186ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=145ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=113ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=259ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=142ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=137ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=219ms TTL=46
Risposta da 94.100.24.92: byte=32 durata=323ms TTL=46

Statistiche Ping per 94.100.24.92:
Pacchetti: Trasmessi = 20, Ricevuti = 20,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 105ms, Massimo = 480ms, Medio = 245ms


C:\Users\Administrator>tracert hentaiverse.org

Traccia instradamento verso hentaiverse.org [94.100.24.92]
su un massimo di 30 punti di passaggio:

1 4 ms 6 ms 5 ms 192.168.43.1
2 * * * Richiesta scaduta.
3 42 ms 51 ms 34 ms xxx.xxx.xxx.xxx
4 49 ms 245 ms 34 ms xxx.xxx.xxx.xxx
5 48 ms 30 ms 34 ms xxx.xxx.xxx.xxx
6 57 ms 39 ms 33 ms 172.17.64.225
7 * * * Richiesta scaduta.
8 272 ms 40 ms * etrunk38.milano50.mil.seabone.net [195.22.196.92]
9 197 ms 41 ms 42 ms et7-3-0-50.milano51.mil.seabone.net [195.22.196.191]
10 215 ms 41 ms 38 ms ntt-verio.milano51.mil.seabone.net [93.186.128.157]
11 242 ms 62 ms 65 ms ae-0.r24.amstnl02.nl.bb.gin.ntt.net [129.250.3.178]
12 115 ms 95 ms 95 ms ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
13 275 ms 76 ms * ae-0.swiftway.amstnl02.nl.bb.gin.ntt.net [81.20.64.62]
14 104 ms 97 ms 101 ms 251.17.100.94.static.swiftway.net [94.100.17.251]
15 119 ms 115 ms 109 ms 92.24.100.94.static.swiftnoc.com [94.100.24.92]


Traccia completata.


NEW DATA:

Microsoft Windows [Versione 6.1.7601]
Copyright © 2009 Microsoft Corporation. Tutti i diritti riservati.

C:\Users\Administrator>ping -n 20 hentaiverse.org

Esecuzione di Ping hentaiverse.org [104.24.7.104] con 32 byte di dati:
Risposta da 104.24.7.104: byte=32 durata=224ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=128ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=286ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=94ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=169ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=476ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=68ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=366ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=74ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=192ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=70ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=68ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=106ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=44ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=472ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=70ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=178ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=296ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=94ms TTL=50
Risposta da 104.24.7.104: byte=32 durata=142ms TTL=50

Statistiche Ping per 104.24.7.104:
Pacchetti: Trasmessi = 20, Ricevuti = 20,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 44ms, Massimo = 476ms, Medio = 180ms


C:\Users\Administrator>tracert hentaiverse.org

Traccia instradamento verso hentaiverse.org [104.24.7.104]
su un massimo di 30 punti di passaggio:

1 3 ms 3 ms 3 ms 192.168.43.1
2 * * * Richiesta scaduta.
3 52 ms 58 ms 33 ms xxx.xxx.xxx.xxx
4 48 ms 27 ms 27 ms xxx.xxx.xxx.xxx
5 159 ms 44 ms 50 ms xxx.xxx.xxx.xxx
6 43 ms 29 ms 33 ms 172.17.66.49
7 * * * Richiesta scaduta.
8 * * * Richiesta scaduta.
9 60 ms 38 ms 50 ms et8-0-2-51.milano51.mil.seabone.net [195.22.205.89]
10 * 62 ms 36 ms cloudflare.milano51.mil.seabone.net [195.22.196.97]
11 127 ms 38 ms 39 ms 104.24.7.104

Traccia completata.

Faster for me too (italy as well)

Some days ago it was 36 ms average from 94.100.24.92

Now it's 17 ms average (13~30 ms in 20 samples) from 104.24.7.104

Now is faster than before.

Ping statistics for 104.24.8.104:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 53ms, Average = 49ms

Before it was 154ms average, but even with that ping I was able to play at 3.8 t/s.

Testing now shows 104.24.8.104 as intended.

Avg ping is all over the place: 62ms, 92ms, 48ms, 92ms, 20ms (!!)

But yes, consistently lower than before the switch. Pathing is significantly reduced in my region.

Pathping:
2 206.80.253.242
3 xe-1-2-1-0.ipr02.totftds.distributel.net [206.80.255.54]
4 cloudflare.ip4.torontointernetxchange.net [206.108.34.208]
5 104.24.8.104

Ping statistics for 104.24.7.104:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 119ms, Average = 112ms

Wow, much faster than before .
My average was 290ms

wow, my HV ping is around 60~90ms now

before , around 200~350ms


err , my old ping is better in term of t/s

kinda hard for me to get 1t/s now with this new 60~90ms

while I can reach 2+t/s with my old ping

This post has been edited by nobody_xxx: Feb 20 2017, 14:21

wow, my HV ping is around 60~90ms now

before , around 200~350ms
err , my old ping is better in term of t/s

kinda hard for me to get 1t/s now with this new 60~90ms

while I can reach 2+t/s with my old ping

Yeah, I have the same problem.
I just played some arenas and it's 2 to 3 times slower than before the switch despite much lower ping.

This post has been edited by milannews: Feb 20 2017, 16:01

From home

CODE

Pinging hentaiverse.org [104.24.7.104] with 32 bytes of data:
Reply from 104.24.7.104: bytes=32 time=26ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=24ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55
Reply from 104.24.7.104: bytes=32 time=29ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55
Reply from 104.24.7.104: bytes=32 time=25ms TTL=55

Ping statistics for 104.24.7.104:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 29ms, Average = 25ms

From work

CODE

Pinging hentaiverse.org [104.24.8.104] with 32 bytes of data:
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=1ms TTL=55
Reply from 104.24.8.104: bytes=32 time=2ms TTL=55

Ping statistics for 104.24.8.104:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

Sounds good.
I'll try to do some arenas when I'm at home to see if there is a difference in speed.

If you got better turns/second before, associate hentaiverse.org with one of the direct IPs in your hosts file. I just did, after doing a WTF???????? when I got a Cloudflare block page while tending my monsters this morning, as it seems it has the default configuration to block various non-standard user agent strings. (Never mind that blocking via UA is completely useless.) And it slaps you with the typical and much-hated "Attention Required!" (captcha) page if you try to access via tor. Every site has to turn that off individually, if they even want to.

"Cloudflare harasses Tor *and* VPN users. Well done, Matthew Prince. You’re doing a fine job of finishing off online privacy. I hope you die a horrific, agonizing death." - Random anon I agree with 100%

Do I want Cloudflare knowing everywhere I go on the web, including Hentaiverse? No, I don't. No, no, no. Why did it have to be that CDN?

Because they're the only ones who will do business with dodgy sites, and they're really cheap? I wonder why that is. It's because we are the product.

[edit]
And it dropped me a __cfduid cookie, meaning they can diddle the contents of the transmission, but I was using HTTPS and the secure certificate did not change. So even if I never allow my browser to connect to HV through Cloudflare again, they've been given hentaiverse.org's private key, and they can give it to other people, who can then silently MITM you any time they want?

This post has been edited by Necromusume: Feb 20 2017, 17:56

It has become slow in Japan.
The ping value became fast (260ms -> 4ms!!!), but hentaiverse turn/sec became very slow (3.0t/s -> 1.0t/s).
Also, some japanse players are saying the same thing.

If you got better turns/second before, associate hentaiverse.org with one of the direct IPs in your hosts file.

Thanks.
Now returned to normal t/s, but I want to feel the 100ms ping!

If you use some e-commerce site that's on Cloudflare, they can get your real name & address thanks to their MITM-SSL. Then you go to hentaiverse, and they get your uid cookie. So they can associate your real name & address with your EH user ID. And the auth cookie is the same as on the rest of the site, so they can read your forum PMs too. Using a CDN like Cloudflare completely negates any benefits of moving to HTTPS.

Ping for 104.24.8.104 is ~ 9ms.
But when I play there is lag sometimes. Mostly on page reload (it takes more time than before).