Working on site part deux

[bord]

Not an expert, but I host WP on nginx at work. A few oddball quirks here and there but overall no complaints. Thanks for your continued work on the site, @randr. Happy 2020.

You need to login in order to like this post: click here

[randr]

Thanks @bord I’m hoping this will be better then Apache but will need to see over the next couple days. Seems better here even in app

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[RYSr (Rich)]

Tried downloading Earthshaker last night, was downloading at around 50-70kb 30 min estimate, canceled it. Tried again this morning now it’s running around 100 KB/s, estimate 15min to download file. I’m using latest Firefox.

Didn’t see any posts about this so thought this would be the right place to let you know, Downloads are normally under a minute.

Rich

You need to login in order to like this post: click here

[randr]

Yea I have noticed this too and honestly nothing I did should have changed this but I am triple checking all settings. Server is located in California and all I can think of is some outage along the way or something. But will update you when/if I find anything.

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

1 user thanked author for this post.

RYSr (Rich)

[randr]

@rysr can you do a tracert vpinball.com (windows) or on mac terminal traceroute vpinball.com

Once the traceroute is run, it generates the report as it goes along the route. Below is a sample traceroute:

C:\>tracert http://www.example.com
Tracing route to example.com [10.10.242.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.10.2
2 * * * Request timed out.
3 2 ms 2 ms 2 ms vbchtmnas9k02-t0-4-0-1.coxfiber.net [216.54.0.29]
4 12 ms 13 ms 3 ms 68.10.8.229
5 7 ms 7 ms 7 ms chndbbr01-pos0202.rd.ph.cox.net [68.1.0.242]
6 10 ms 8 ms 9 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
7 10 ms 9 ms 10 ms 100ge7-1.core1.nyc4.he.net [184.105.223.166]
8 72 ms 84 ms 74 ms 10gr10-3.core1.lax1.he.net [72.52.92.226]
9 76 ms 76 ms 90 ms 10g1-3.core1.lax2.he.net [72.52.92.122]
10 81 ms 74 ms 74 ms 205.134.225.38
11 72 ms 71 ms 72 ms http://www.inmotionhosting.com [192.145.237.216]
As you can see, there are several rows divided into columns on the report. Each row represents a “hop” along the route. Think of it as a check-in point where the signal gets its next set of directions. Each row is divided into five columns. A sample row is below:

10 81 ms 74 ms 74 ms 205.134.225.38
Let’s break this particular hop down into its parts.

Hop #
RTT 1
RTT 2
RTT 3
Name/IP Address
10
81 ms
74 ms
74 ms
205.134.225.38
Hop Number – This is the first column and is simply the number of the hop along the route. In this case, it is the tenth hop.

RTT Columns – The next three columns display the round trip time (RTT) for your packet to reach that point and return to your computer. This is listed in milliseconds. There are three columns because the traceroute sends three separate signal packets. This is to display consistency, or a lack thereof, in the route.

Domain/IP column – The last column has the IP address of the router. If it is available, the domain name will also be listed.

Checking the hop times
The times listed in the RTT columns are the main thing you want to look at when evaluating a traceroute. Consistent times are what you are looking for. There may be specific hops with increased latency times but they may not indicate that there is an issue. You need to look at a pattern over the whole report. Times above 150ms are considered to be long for a trip within the continental United States. (Times over 150ms may be normal if the signal crosses an ocean, however.) but issues may show up with very large numbers.

Increasing latency towards the target
If you see a sudden increase in a hop and it keeps increasing to the destination (if it even gets there), then this indicates an issue starting at the hop with the increase. This may well cause packet loss where you will even see asterisks (*) in the report.

1 10 ms 7 ms 9 ms 172.16.10.2
2 78 ms 100 ms 32 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
3 78 ms 84 ms 75 ms 100ge7-1.core1.nyc4.he.net [184.105.223.166]
4 782 ms 799 ms * ms 10gr10-3.core1.lax1.he.net [72.52.92.226]
5 * ms 899 ms 901 ms 10g1-3.core1.lax2.he.net [72.52.92.122]
6 987 ms 954 ms 976 ms 205.134.225.38
7 1002 ms 1011 ms 999 ms http://www.inmotionhosting.com [192.145.237.216]
High latency in the middle but not at beginning or end
If the hop immediately after a long one drops back down, it simply means that the router at the long hop set the signal to a lower priority and does not have an issue. Patterns like this do not indicate an issue.

1 <1 ms <1 ms <1 ms 173.247.246.116
2 30 ms 7 ms 11 ms 10.10.0.2
3 200 ms 210 ms 189 ms 4.71.136.1
4 111 ms 98 ms 101 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
5 99 ms 100 ms 98 ms 205.134.225.38
High latency in the middle that remains consistent
If you see a hop jump but remain consistent throughout the rest of the report, this does not indicate an issue.

1 <1 ms <1 ms <1 ms 173.247.246.116
2 30 ms 7 ms 11 ms 10.10.0.2
3 93 ms 95 ms 92 ms 4.71.136.1
4 95 ms 99 ms 101 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
5 99 ms 100 ms 98 ms 100ge7-1.core1.nyc4.he.net [184.105.223.166]
6 95 ms 95 ms 95 ms 10g1-3.core1.lax2.he.net [72.52.92.122]
7 95 ms 96 ms 94 ms 205.134.225.38]
High latency in the beginning hops
Seeing reported latency in the first few hops indicates a possible issue on the local network level. You will want to work with your local network administrator to verify and fix it.

Timeouts at the beginning of the report
If you have timeouts at the very beginning of the report, say within the first one or two hops, but the rest of the report runs, do not worry. This is perfectly normal as the device responsible likely does not respond to traceroute requests.

Timeouts at the very end of the report
Timeouts at the end may occur for a number of reasons. Not all of them indicate an issue, however.

The target’s firewall may be blocking requests. The target is still most probably reachable with a normal HTTP request, however. This should not affect normal connection.
The return path may have an issue from the destination point. This would mean the signal is still reaching, but just not getting the return signal back to your computer. This should not affect normal connection.
Possible connection problem at the target. This will affect the connection.

Do I need to contact my hosting company?
Once you have found a hop that seems to have an issue, you can identify its location and determine where the issue lies. It may be within your network, your ISP, somewhere along the route, or within your hosting provider’s domain.

The first hop is within your own network. The next hop is your ISP. The last couple of hops are likely within your hosting providers’ domain and control, so if the issue is there, they may be able to fix it for you. If it is anywhere prior to that, the issue is simply along the route and is within neither your nor your hosting provider’s control.

 

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[JR]

Just d-loaded the Earthshaker update.  400-500 KB/s, took around 5 minutes.  That’s about right on my slow home network.

 

Happy New Year!  Go eat some sauerkraut!

You need to login in order to like this post: click here

[RYSr (Rich)]

@randar

I just tried the download again and it also ran at 500KB/s and took around 5min. Normal for me is around 5-10 seconds.

I ran the trace route here from NJ 08619, It took 21 hops, timed out on hops 2 and 7, an all RTT times looked even across all three packets. RTT of 1ms for hop 1, increasing to 80ms for inmotionhosting hops 18,19,and 20, then 85ms for vpinball.com on hop 21. Doesn’t appear to be a router problem..

I ran a trace for VPF and it took 16 hops with similar RTT times, but a test file download took only 3 seconds for the table.

 

You need to login in order to like this post: click here

[JR]

It’s usually much quicker at work where I do most of my downloads.  Usually under 2 minutes.  Will check that tomorrow.

You need to login in order to like this post: click here

[Skitso]

Site’s been oddly slow for a few days with my android tablet. Everything seems normal with my desktop and ipad… Really strange

You need to login in order to like this post: click here

[rothbauerw]

I’ve had no issues here.  Just downloaded Earthshaker in 37.37 seconds.

Current Project: Perpetual updates of VPX physics.

You need to login in order to like this post: click here

[randr]

I truly think it’s just your location and how you are getting to server and whatever stop it makes on the way there is an issue. I have slow downs here aswell I will contact my isp(Comcast) as it’s really their issue not server/host issue. I’ll letcha know what I find out

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[randr]

From my traceroute I found this IP: 96.120.48.149.  This is a comcast/xfinity relay server and from downdetector.com it has been having issues.  Here is the iptrace showing the location of the server:
https://www.ip-tracker.org/locator/ip-lookup.php?ip=96.120.48.149

If you scroll down you will see the server is near Wichita, Kansas.

Here is the Downdetector.commap for Xfinity/Comcast:
https://downdetector.com/status/comcast-xfinity/map/

If you zoom right to the center of the map, you will see a orange area around the same area where that relay server is located.

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[STAT]

Have some “Troubles” since some Days, load Page over IE, Downloads and so on are ok,
but when i scroll down and read a Thread, it stuck, have to wait some Secounds to read the next Post and CPU Comes close to 100%, Laptop Fan goes on …

Whatever, Happy New Year randr

You need to login in order to like this post: click here

[Rajo Joey]

I also have terrible loads of the site and the downloads. And it’s the only site, which is so slow. I don’t see this on another.
I just download three files and the estimated time is nearly one hour. Normaly I’ve got this three dl in a few seconds. I have 400 mbit.

Here is the route.
1 <1 ms <1 ms <1 ms FRITZCHEN [192.168.178.1]
2 14 ms 17 ms 9 ms ip4d16b9fe.dynamic.kabel-deutschland.de [77.22.185.254]
3 9 ms 13 ms 9 ms ip53a99a36.static.kabel-deutschland.de [83.169.154.54]
4 10 ms 51 ms 13 ms ip5886c253.static.kabel-deutschland.de [88.134.194.83]
5 14 ms 17 ms 12 ms ip5886bb17.dynamic.kabel-deutschland.de [88.134.187.23]
6 16 ms 13 ms 14 ms 145.254.3.64
7 14 ms 13 ms 16 ms 145.254.2.215
8 20 ms 19 ms 19 ms ae9-100-xcr1.hac.cw.net [195.89.99.1]
9 25 ms 19 ms 25 ms ae31-xcr2.fix.cw.net [195.2.2.138]
10 19 ms 21 ms 21 ms be3001.agr41.fra03.atlas.cogentco.com [130.117.14.73]
11 18 ms 22 ms 20 ms be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118]
12 30 ms 30 ms 30 ms be2800.ccr42.par01.atlas.cogentco.com [154.54.58.238]
13 103 ms 105 ms 101 ms be3628.ccr42.jfk02.atlas.cogentco.com [154.54.27.169]
14 109 ms 110 ms 108 ms be2807.ccr42.dca01.atlas.cogentco.com [154.54.40.110]
15 120 ms 117 ms 119 ms be2113.ccr42.atl01.atlas.cogentco.com [154.54.24.222]
16 146 ms 145 ms 149 ms be2690.ccr42.iah01.atlas.cogentco.com [154.54.28.130]
17 176 ms 178 ms 175 ms be2928.ccr21.elp01.atlas.cogentco.com [154.54.30.162]
18 177 ms 176 ms 174 ms be2930.ccr32.phx01.atlas.cogentco.com [154.54.42.77]
19 177 ms 176 ms 175 ms be2932.ccr42.lax01.atlas.cogentco.com [154.54.45.162]
20 176 ms 178 ms 175 ms be2918.rcr21.b002695-3.lax01.atlas.cogentco.com [154.54.41.194]
21 173 ms 175 ms 175 ms 38.142.230.226
22 176 ms 177 ms 175 ms tge4-1-dc1-core-1.corporatecolo.com [66.117.1.86]
23 175 ms 176 ms 172 ms csw3.lax1.inmotionhosting.com [198.46.92.2]
24 177 ms 176 ms 174 ms csw4.lax1.inmotionhosting.com [198.46.92.3]
25 175 ms 174 ms 176 ms csw1.lax1.inmotionhosting.com [198.46.92.26]
26 176 ms 175 ms 173 ms server.vpinball.com [192.249.122.14]
Many hops…
I hope, it will be better in the next days. I’ve never see such slow response from vpinball.

You need to login in order to like this post: click here

[randr]

Good information thank you!

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[Thalamus]

Huh. That is awful, I’ve got only 14 hops before reaching vpinball.com

You need to login in order to like this post: click here

[JR]

Hm.  Just d-loaded Earthshaker on my much faster work connection in under a minute.

Here’s my tracert report:

You need to login in order to like this post: click here

[randr]

Called Comcast my ISP what a waste of time that was. So i connected my home desktop to my cell phones cellular hot spot and could download 100mb from downloads section in 20 sec and if i use my Comcast internet it takes 25 min for same file. So i think its safe to say something is up but related to my routes to server and i am sure its what some others are seeing as well. CRAZY the my phones cellular data is faster then my $300 a month Comcast internet! Anyways lets hope enough people complain and they fix whatever station is causing issues soon.

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[Tom]

I have no clue what you guys are talking about on this thread, lol.  @randr I think you like this stuff more than playing pinball!

You need to login in order to like this post: click here

[JR]

Tom wrote:

I have no clue what you guys are talking about on this thread, lol. @randr I think you like this stuff more than playing pinball

Ha.  Neither do I.  I’m not sure I understand anything I’m doing here.

You need to login in order to like this post: click here

[Author]

Posts