So here we are.. another Saturday night and if I look at the clock, we're right on time... severe inability to connect to R3's master servers at 7:30pm ET... oh and look someone in our group from NewYork (600mi away) has the same issue.. geez .. I wonder what it is? That this happens regularly on a Sat eve here in the GMT-4 should be a clue of sorts... Again, there IS an issue and it appears to be with the R3 system or the ISP that services R3. But there is no way to really figure this out without help from inside R3. *IF* R3 would work *with us* on this issue, it would be a great step forward in building some trust. Just now it took over 3 min for the Server menu to load, after it took several more minutes for the program to actually load. We can see that large amounts of data are being sent to R3 system, perhaps the R3 list servers are overloaded? getting DOS attacks? Maybe your ISP does scheduled maintenance at 1am on a regular basis?? here is a connection test log... there is adequate capacity and speed available on my end. (I just did test.. 5:30 seconds from program load request to eventual Error 13. Video coming.) 0.00s Start testing DSL 00.01s geo location failed 00.13s Servers available: 9 00.18s pinging 8 locations 05.19s 26ms Newcastle, Delaware, USA 05.19s 47ms Nashville, TN, USA 05.19s 63ms Dallas, USA 05.19s 65ms Houston, USA 05.19s 94ms Beaverton, Oregon, USA 05.19s 94ms Los Angeles 2, CA, USA 05.19s 95ms San Jose, USA 05.2s could not reach Kansas City, Missouri, USA http://t50.dslreports.com 05.21s 5 seconds measuring idle buffer bloat 10.42s Trial download normal 10.44s Using GET for upload testing 18.61s stream0 1.13 megabit Newcastle, Delaware, USA 18.61s stream1 1.29 megabit Dallas, USA 18.61s stream2 0.7 megabit Dallas, USA 18.61s stream3 0.75 megabit Dallas, USA 18.61s stream4 0.63 megabit Dallas, USA 18.61s stream5 0.22 megabit Newcastle, Delaware, USA 18.61s stream6 0.57 megabit Nashville, TN, USA 18.61s stream7 0.49 megabit Newcastle, Delaware, USA 23.45s End of download testing. Starting upload in 2 seconds 25.47s Capping upload streams to 2 because of download result 25.47s starting websocket upload with 2 streams 25.47s minimum upload speed of 0.31 per stream 25.6s sent first packet to t68.dslreports.com 26.35s sent first packet to t59.dslreports.com 26.62s got first reply from t68.dslreports.com 118050 27.52s got first reply from t59.dslreports.com 11805 44.62s Recording upload 0.65 44.62s Timer drops: frames=0 total ms=0 44.63s END TEST 46.63s Total megabytes consumed: 10.8 (down:8.5 up:2.3)
I [m facing this same Error 13, since months ago. Today the is happening again. Just minutes ago, researching on the web for a solution, I did some things like? 1) Verify Files Integrity on the Steam 2) Set the DNS adresses to Auto, since I like to use fixed. 3) Restart the Computer ..... I have already oppened a ticket request before, twice or three times. I Never had a response from Sector 3. Please Guys(SCT3) us an information if this is about the Steam Server or the Sector 3 Server or my Network Conection. I saw the even using VPN some users still gets the problem. Kr
There is absolutely no reason to start another topic about the same issue: https://forum.sector3studios.com/index.php?threads/connection-issues-error-13.16644 So, if you're not going to listen in that other topic, I'll try again here: This shows that **your connection** does not reach Kansas City, Missouri Other than that, it shows absolutely nothing since the R3E servers are located in Europe, not USA, and this is simply a random speedtest. Like I said earlier, it is the route from America (North/South) to Europe. **SOME** users have issues, not ALL of them. That means it's something on the network side, not the server side - otherwise NOBODY would be able to connect. It really is that simple. Which is also the reason that when you used the VPN to connect, it worked. Which means it's network based. Not R3E's fault. For the record, a bug report has been made. A possible solution is proposed. But it's not an easy or cheap solution, so it is going to take some time.
You know.. instead of continually ripping me a new one, how about just relay the information you have and not get personal about it? *I* am trying to work with R3 to resolve this, not you... thank for your input.
Please use the link provided. https://forum.sector3studios.com/index.php?threads/connection-issues-error-13.16644/ Locking this thread