RMN IS UP! NO, IT'S DOWN. NOW IT'S UP! OH WAIT... DOWN AGAIN.
Posts
author=LockeZ
Sounds like a personal problem. Get some Cialis and it will stay up when you need it. It's never been a problem for me, but I'm not judging, I know these things can happen with older hardware.
haha Good one xD
It wouldn't be a hardware issue, that was just part of his joke, but 99% of the time in a situation like this it is a local issue. If it wasn't a local issue, everyone would be affected. Diagnosing these kinds of issues sucks, so...sucks to thou who art affected.
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
5958
Well, it could be his router. Or his wireless adapter. Or the wiring in his walls. Or the network equipment at his internet service provider's building.
That last one is probably the most likely. But the first two are a lot easier to test and to do something about if they're the problem.
That last one is probably the most likely. But the first two are a lot easier to test and to do something about if they're the problem.
...except that only RMN was ever affect for me. Other sites and internet access were not affected. (And seeing as how I work in an office that depends on network and internet access, someone would have piped up about internet issues!).
It started happening for me around the same time that that story about thunderstorms in the NE of the USA that took out a ton of server farms and took down Pinterest and Amazon something or other a couple weeks ago.
It started happening for me around the same time that that story about thunderstorms in the NE of the USA that took out a ton of server farms and took down Pinterest and Amazon something or other a couple weeks ago.
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
5958
Guess the tubes are just clogged somewhere between you and the pot of rmn noodles.
author=kentonayou should check out with the server if there a problems (that usually solve it) and if rmn servers is under a server provider you should also contact them for assistant. and do you have weekly/monthly maintenance? this usually solve the servers problems.
...except that only RMN was ever affect for me. Other sites and internet access were not affected. (And seeing as how I work in an office that depends on network and internet access, someone would have piped up about internet issues!).
It started happening for me around the same time that that story about thunderstorms in the NE of the USA that took out a ton of server farms and took down Pinterest and Amazon something or other a couple weeks ago.
I asked the server. He said he was doing just fine. Maybe he doesn't like server maintenance and was lying?
I'll dig into it further.
I'll dig into it further.
This *just* happened to me. I can safely say it has nothing to do with the server. It is a DNS issue. Maybe I will look at moving our DNS locally (this will cause downtime).
A DNS server that you use or your ISP uses has lost contact with one of the DNS servers it uses (or perhaps one of the root DNS servers) and can't lookup rpgmaker.net to find out where it should go. Or maybe it couldn't contact the Nameservers.
I'm not sure if moving the DNS locally will even help, but it's worth a try.
I'm not sure if moving the DNS locally will even help, but it's worth a try.
It just happened to me 10 mins ago, and again RMN's server was up but I couldn't connect. A few refreshes finally got to it.
So it means rpgmaker.net's DNS server is having problems (which could they be?) or that it's under attack?
Some other things that could help diagnose the problem:
When this happens to you, run nslookup/dig and tracert/traceroute then post your results here.
In Windows, go to a command prompt and type nslookup rpgmaker.net and tracert rpgmaker.net
In Mac OS X or Linux, go to a terminal session and type dig rpgmaker.net and traceroute rpgmaker.net
When this happens to you, run nslookup/dig and tracert/traceroute then post your results here.
In Windows, go to a command prompt and type nslookup rpgmaker.net and tracert rpgmaker.net
In Mac OS X or Linux, go to a terminal session and type dig rpgmaker.net and traceroute rpgmaker.net
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
5958
Tracing route to rpgmaker.net
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 231 ms 143 ms 147 ms CPE-65-28-18-197.kc.res.rr.com
4 170 ms 179 ms 170 ms CPE-69-76-62-253.kc.res.rr.com
5 185 ms 176 ms 182 ms ae-4-0.cr0.chi10.tbone.rr.com
6 179 ms 179 ms 165 ms ae-0-0.pr0.chi10.tbone.rr.com
7 170 ms 177 ms 164 ms xe-10-0-0.edge2.Chicago2.Level3.net
8 183 ms 188 ms 174 ms vl-3602-ve-226.ebr2.Chicago2.Level3.net
9 183 ms 143 ms 170 ms ae-5-5.ebr2.Chicago1.Level3.net
10 198 ms 189 ms 212 ms ae-3-3.ebr2.Atlanta2.Level3.net
11 217 ms 199 ms 195 ms ae-26-52.car2.Atlanta2.Level3.net
12 207 ms 212 ms 199 ms IMMEDION-LL.car2.Atlanta2.Level3.net
13 217 ms 218 ms 204 ms 67.23.161.138
14 213 ms 206 ms 220 ms 67.23.161.133
15 67.23.177.196 reports: Destination protocol unreachable.
nslookup rpgmaker.net
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: rpgmaker.net
Address: 67.23.177.196
Just happened. Lasted at least twenty minutes for me, and I couldn't connect on my cell phone either. About halfway through it did actually let me on for a few seconds, after taking a full minute to connect. Let me open this thread, and submit this post, but if I open another tab and try to connect again, it fails. As long as I stay within this tab that's already on the site, it seems to be fine.
I considered running tracert from my phone but decided that by the time I figured out how the site would be back up.
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 231 ms 143 ms 147 ms CPE-65-28-18-197.kc.res.rr.com
4 170 ms 179 ms 170 ms CPE-69-76-62-253.kc.res.rr.com
5 185 ms 176 ms 182 ms ae-4-0.cr0.chi10.tbone.rr.com
6 179 ms 179 ms 165 ms ae-0-0.pr0.chi10.tbone.rr.com
7 170 ms 177 ms 164 ms xe-10-0-0.edge2.Chicago2.Level3.net
8 183 ms 188 ms 174 ms vl-3602-ve-226.ebr2.Chicago2.Level3.net
9 183 ms 143 ms 170 ms ae-5-5.ebr2.Chicago1.Level3.net
10 198 ms 189 ms 212 ms ae-3-3.ebr2.Atlanta2.Level3.net
11 217 ms 199 ms 195 ms ae-26-52.car2.Atlanta2.Level3.net
12 207 ms 212 ms 199 ms IMMEDION-LL.car2.Atlanta2.Level3.net
13 217 ms 218 ms 204 ms 67.23.161.138
14 213 ms 206 ms 220 ms 67.23.161.133
15 67.23.177.196 reports: Destination protocol unreachable.
nslookup rpgmaker.net
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: rpgmaker.net
Address: 67.23.177.196
Just happened. Lasted at least twenty minutes for me, and I couldn't connect on my cell phone either. About halfway through it did actually let me on for a few seconds, after taking a full minute to connect. Let me open this thread, and submit this post, but if I open another tab and try to connect again, it fails. As long as I stay within this tab that's already on the site, it seems to be fine.
I considered running tracert from my phone but decided that by the time I figured out how the site would be back up.
So, turns out this actually probably wasn't a DNS issue and is probably related to problems at the datacenter where our server is hosted. I'll try to see if I can find out more about today's outage as well as the ongoing issues we have been having.
I couldn't connect for quite a while just then, here's what I've got :
traceroute to rpgmaker.net (67.23.177.196), 30 hops max, 60 byte packets
1 freebox-server.local (192.168.1.254) 3.533 ms 3.527 ms 3.529 ms
2 82.227.211.254 (82.227.211.254) 128.446 ms 128.442 ms 128.437 ms
3 * * *
4 marseille-6k-1-po1.intf.routers.proxad.net (212.27.57.113) 128.392 ms 129.845 ms 129.850 ms
5 bzn-crs16-1-be1104.intf.routers.proxad.net (212.27.50.185) 158.018 ms 158.022 ms 158.027 ms
6 te0-2-0-6.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 158.029 ms 131.017 ms 131.006 ms
7 te0-3-0-6.mpd21.par01.atlas.cogentco.com (130.117.50.66) 123.892 ms te0-7-0-7.mpd22.par01.atlas.cogentco.com (154.54.60.33) 123.887 ms 123.876 ms
8 te0-7-0-7.mpd22.jfk02.atlas.cogentco.com (154.54.46.105) 203.907 ms te0-2-0-5.mpd22.jfk02.atlas.cogentco.com (154.54.7.33) 203.917 ms te0-7-0-7.mpd22.jfk02.atlas.cogentco.com (154.54.46.105) 203.907 ms
9 te0-2-0-1.ccr21.jfk05.atlas.cogentco.com (154.54.46.250) 209.409 ms te0-1-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.31.6) 209.414 ms te0-2-0-5.ccr21.jfk05.atlas.cogentco.com (154.54.46.254) 209.419 ms
10 level3.jfk05.atlas.cogentco.com (154.54.12.250) 209.422 ms Te-8-1.car2.NewYork1.Level3.net (4.68.111.45) 215.244 ms level3.jfk05.atlas.cogentco.com (154.54.11.218) 224.669 ms
11 vlan70.csw2.NewYork1.Level3.net (4.69.155.126) 224.669 ms vlan60.csw1.NewYork1.Level3.net (4.69.155.62) 226.287 ms 226.277 ms
12 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 227.831 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 222.455 ms ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 228.794 ms
13 ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 228.785 ms 230.360 ms 230.348 ms
14 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 232.500 ms 232.491 ms 232.479 ms
15 ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 280.753 ms 253.268 ms 254.070 ms
16 ae-16-51.car2.Atlanta2.Level3.net (4.69.150.6) 253.505 ms 398.825 ms 398.822 ms
17 * * *
traceroute to rpgmaker.net (67.23.177.196), 30 hops max, 60 byte packets
1 freebox-server.local (192.168.1.254) 3.533 ms 3.527 ms 3.529 ms
2 82.227.211.254 (82.227.211.254) 128.446 ms 128.442 ms 128.437 ms
3 * * *
4 marseille-6k-1-po1.intf.routers.proxad.net (212.27.57.113) 128.392 ms 129.845 ms 129.850 ms
5 bzn-crs16-1-be1104.intf.routers.proxad.net (212.27.50.185) 158.018 ms 158.022 ms 158.027 ms
6 te0-2-0-6.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 158.029 ms 131.017 ms 131.006 ms
7 te0-3-0-6.mpd21.par01.atlas.cogentco.com (130.117.50.66) 123.892 ms te0-7-0-7.mpd22.par01.atlas.cogentco.com (154.54.60.33) 123.887 ms 123.876 ms
8 te0-7-0-7.mpd22.jfk02.atlas.cogentco.com (154.54.46.105) 203.907 ms te0-2-0-5.mpd22.jfk02.atlas.cogentco.com (154.54.7.33) 203.917 ms te0-7-0-7.mpd22.jfk02.atlas.cogentco.com (154.54.46.105) 203.907 ms
9 te0-2-0-1.ccr21.jfk05.atlas.cogentco.com (154.54.46.250) 209.409 ms te0-1-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.31.6) 209.414 ms te0-2-0-5.ccr21.jfk05.atlas.cogentco.com (154.54.46.254) 209.419 ms
10 level3.jfk05.atlas.cogentco.com (154.54.12.250) 209.422 ms Te-8-1.car2.NewYork1.Level3.net (4.68.111.45) 215.244 ms level3.jfk05.atlas.cogentco.com (154.54.11.218) 224.669 ms
11 vlan70.csw2.NewYork1.Level3.net (4.69.155.126) 224.669 ms vlan60.csw1.NewYork1.Level3.net (4.69.155.62) 226.287 ms 226.277 ms
12 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 227.831 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 222.455 ms ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 228.794 ms
13 ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 228.785 ms 230.360 ms 230.348 ms
14 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 232.500 ms 232.491 ms 232.479 ms
15 ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 280.753 ms 253.268 ms 254.070 ms
16 ae-16-51.car2.Atlanta2.Level3.net (4.69.150.6) 253.505 ms 398.825 ms 398.822 ms
17 * * *
Twice today I got the error that says something along the lines of "Oops, there was a problem. We are probably aware". I hit reload and it loaded the page. Not sure if it's related.
author=Link_2112
Twice today I got the error that says something along the lines of "Oops, there was a problem. We are probably aware". I hit reload and it loaded the page. Not sure if it's related.
No, not related at all. That is a different error.

















