Is R2R running slow for you?

[revhtree Verified Admin]

Is R2R running slow for you?

 

[Coffee Soundboard]

Seems fine to me.

 

[Dan Palmer]

Actually just got a 521 error from cloudflare saying the webserver isn't responding.

 

[Troylee]

For me it is.. I actually just got an error message and it said your server was down.. if you’re a visitor please try again later! If you’re the owner please contact your host..

 

[Reefer Matt]

It comes and goes, but does hang up sometimes.

 

[Coffee Soundboard]

For me it is.. I actually just got an error message and it said your server was down.. if you’re a visitor please try again later! If you’re the owner please contact your host..

I just got that too!

 

[fishguy242]

same here ,of and on speed lately,more than the usual host down over past week or so ?

 

[SaltyCabbage]

Yup, on mobile it started about an hour ago. I could not load any threads and would get an error message and the page would crash white after. It seems to be better now though, but still slow to load threads.

 

[Sharkbait19]

Depends on the time - sometimes it runs great but other times it’s really slow. I’ve always just equated that to a lot of traffic or poor reception though.

 

[Cell]

I feel like the internet in general has been running slow lately...thought it was my phone at first or my home network but it's been spotty at work too.

 

[robotrash]

Seems fine to me, no errors. I have it installed as a web app on my device on gigabit wifi at home.

 

[sfmacguy]

Yeah, there's some latency spikes happening.


64 bytes from 104.26.7.83: icmp_seq=0 ttl=52 time=12.612 ms


64 bytes from 104.26.7.83: icmp_seq=1 ttl=52 time=15.034 ms


64 bytes from 104.26.7.83: icmp_seq=2 ttl=52 time=139.660 ms


64 bytes from 104.26.7.83: icmp_seq=3 ttl=52 time=136.134 ms


64 bytes from 104.26.7.83: icmp_seq=4 ttl=52 time=11.872 ms


64 bytes from 104.26.7.83: icmp_seq=5 ttl=52 time=12.240 ms


64 bytes from 104.26.7.83: icmp_seq=6 ttl=52 time=100.906 ms


64 bytes from 104.26.7.83: icmp_seq=7 ttl=52 time=143.614 ms


64 bytes from 104.26.7.83: icmp_seq=8 ttl=52 time=17.920 ms

 

[Reefkeepers Archive]

I did just get an error message

 

[areefer01]

Yeah, there's some latency spikes happening.


64 bytes from 104.26.7.83: icmp_seq=0 ttl=52 time=12.612 ms


64 bytes from 104.26.7.83: icmp_seq=1 ttl=52 time=15.034 ms


64 bytes from 104.26.7.83: icmp_seq=2 ttl=52 time=139.660 ms


64 bytes from 104.26.7.83: icmp_seq=3 ttl=52 time=136.134 ms


64 bytes from 104.26.7.83: icmp_seq=4 ttl=52 time=11.872 ms


64 bytes from 104.26.7.83: icmp_seq=5 ttl=52 time=12.240 ms


64 bytes from 104.26.7.83: icmp_seq=6 ttl=52 time=100.906 ms


64 bytes from 104.26.7.83: icmp_seq=7 ttl=52 time=143.614 ms


64 bytes from 104.26.7.83: icmp_seq=8 ttl=52 time=17.920 ms

The main way to tell is have Rev or the admins look at the data it is hosted at. Or if they are using Google analytics or other tools similar on the hosted platform.

Is it slow can be anything from local network to client accessing content to ISP and WAN. Want to know if it is slow or not just look at the data you have Rev and Bob is your Uncle. Time taken / page should be readily available if the other means are not available.

As an aside in the Northern California network side of things, Comcast, the site is fine in my user experience.

 

[revhtree Verified Admin]

Should be better now.