insanelymac has been really hard to access for a couple off days anybody else had the same problem?

starobrno1 · June 21, 2012

Cool its working again. Thanks guys was a little bit worried authorities where I live wanted to shut me out from here.

Thanks again

Foxic · June 22, 2012

Traceroute:

traceroute to www.insanelymac.com (87.124.44.2), 64 hops max, 72 byte packets
1  10.108.48.1 (10.108.48.1)  7.356 ms  5.927 ms  6.619 ms
2  cosh-core-1a-ae1-1007.network.virginmedia.net (80.3.162.253)  17.847 ms  7.130 ms  7.382 ms
3  winn-bb-1a-ae2-0.network.virginmedia.net (212.43.163.209)  11.347 ms  9.205 ms  13.266 ms
4  popl-bb-1b-as5-0.network.virginmedia.net (212.43.162.194)  12.051 ms  12.072 ms  13.124 ms
5  popl-bb-1a-ae0-0.network.virginmedia.net (213.105.174.229)  12.009 ms  12.213 ms  12.115 ms
6  nrth-bb-1b-as3-0.network.virginmedia.net (213.105.172.13)  66.006 ms  13.000 ms  22.125 ms
7  tele-ic-4-ae0-0.network.virginmedia.net (62.253.174.18)  58.106 ms  15.140 ms  14.234 ms
8  linx1.thn.fubra.net (195.66.225.33)  14.564 ms  14.343 ms  14.264 ms
9  87.124.32.94 (87.124.32.94)  16.345 ms  16.770 ms  17.112 ms
10  insanelymac.com (87.124.44.2)  17.379 ms  17.173 ms  16.370 ms

And to /forum:

traceroute to www.insanelymac.com/forum (81.200.64.50), 64 hops max, 72 byte packets
1  10.108.48.1 (10.108.48.1)  6.667 ms  5.640 ms  5.905 ms
2  cosh-core-1a-ae1-1007.network.virginmedia.net (80.3.162.253)  6.247 ms  5.983 ms  6.846 ms
3  winn-bb-1a-ae2-0.network.virginmedia.net (212.43.163.209)  10.659 ms  10.400 ms  9.989 ms
4  brnt-bb-1b-as5-0.network.virginmedia.net (213.105.172.234)  13.914 ms  12.675 ms  11.973 ms
5  brnt-bb-1a-ae0-0.network.virginmedia.net (213.105.174.225)  11.017 ms  10.578 ms  10.953 ms
6  port-channel100.ar7.ams2.gblx.net (64.213.176.61)  23.399 ms  24.044 ms  24.361 ms
7  po6.ar4.lon3.gblx.net (67.16.142.102)  24.820 ms  23.795 ms  23.384 ms
8  nominum.port-c2.552.406.ar4.lon3.gblx.net (64.210.69.250)  27.495 ms  25.691 ms  26.189 ms
9  81.200.66.253 (81.200.66.253)  23.861 ms  24.634 ms  25.982 ms
10  advancedsearch.virginmedia.com (81.200.64.50)  27.626 ms  27.092 ms  28.818 ms

Ed · June 28, 2012

Guys, anyone else in this thread still been having connection problems?

3.14r2 · June 29, 2012

I did about 10-20 minutes ago. Now seem to work again.

Kasakka · August 28, 2012

What I keep seeing is that trying to open a page can just stall but clicking the link again almost immediately makes it open. It doesn't seem to matter what page it is, anything on this site causes it. Using Google Chrome, same thing happens on OSX and Windows. No proxy in use.

This is really annoying when trying to search for anything and I have not seen it happen on any site. It's been going on for months for me and during that time operating systems have been reinstalled so it's not my computer.

cat_7 · August 29, 2012

During the last 2 weeks I have been having massive problems to get the front page to load. Sometimes the forum was also hard to reach after the front page finally showed. Today is the first time since then that the site behaved normally.

Best,

Cat_7

p.H · August 29, 2012

Im still having problems accessing insanelymac but I found this work around so if you have the same troubles as I have just go to www.hidemyass.com and klick google and then type in insanelymac.com. Hopefully it will work for you too, it did for me twice now so it probably will. The page loads with the search bar/google set on hide my ass so hit enter and when your on google type in insanelymac and hit enter again. This is the first post Im able to do from my own network in over one week. Im thinking Apple is trying to shut down access to this place, at least where I live (europe). Good luck guys

maybe it's not in relationship with Apple

like you've said, when using windows, you still can't make yourself succeed in entering this site

I do believe proxy will help cuz i am the one using proxy

Ed · August 29, 2012

Guys, could you post your ISP name and traceroute output please so we can look further into this?

eep357 · August 29, 2012

I've been fine for quite a while now, maybe manually changing dns to google may help?

cat_7 · August 31, 2012

Hi, I believe the issue is not so much finding insanelymac.com, but rather some processing on the site. F.i., even when the homepage is shown after "normal" time (indicating DNS is working OK), the site can hang for minutes after I click "more" in e.g. one of the news items.

Perhaps interesting is this: whenever I enter your ip-address (87.124.44.2) directly in my browser I get a page with the Insanelymac background but with a 404 error where the news would normally show up.

Nevertheless: my provider is internl.net

Tracing route to insanelymac.com [87.124.44.2]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 16 ms 15 ms 15 ms bbned1.surfrt.nik-asd.internl.net [217.149.196.50]

3 16 ms 15 ms 15 ms ge2-20.newxr1.nik-asd.internl.net [217.149.196.51]

4 16 ms 15 ms 16 ms AE3.2118.JNR01.Asd002A.surf.net [145.145.19.61]

5 16 ms 16 ms 15 ms AE1.500.JNR02.Asd001A.surf.net [145.145.80.73]

6 16 ms 16 ms 16 ms ge-11-2-4.er1.ams1.nl.above.net [64.125.12.53]

7 84 ms 16 ms 17 ms ge-2-2-0.mpr1.ams1.nl.above.net.24.125.64.in-addr.arpa [64.125.24.213]

8 24 ms 21 ms 21 ms ge-1-1-0.mpr1.lhr3.uk.above.net [64.125.27.221]

9 21 ms 21 ms 22 ms xe-3-0-0.mpr2.lhr3.uk.above.net [64.125.27.158]

10 24 ms 21 ms 21 ms xe-1-0-0.mpr1.lhr8.uk.above.net [64.125.28.206]

11 23 ms 22 ms 22 ms 94.31.35.219.available.above.net [94.31.35.219]

12 24 ms 24 ms 23 ms 87.124.32.97

13 25 ms 24 ms 24 ms r1s.c2.catn.com [87.124.43.21]

14 24 ms 24 ms 24 ms insanelymac.com [87.124.44.2]

Trace complete.

Mr.D. · August 31, 2012

Microsoft Windows [Version 6.1.7601]

C:\Users\Tim>ping 87.124.44.2

Pinging 87.124.44.2 with 32 bytes of data:

Reply from 87.124.44.2: bytes=32 time=135ms TTL=128

Reply from 87.124.44.2: bytes=32 time=136ms TTL=128

Reply from 87.124.44.2: bytes=32 time=133ms TTL=128

Reply from 87.124.44.2: bytes=32 time=136ms TTL=128

Ping statistics for 87.124.44.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 133ms, Maximum = 136ms, Average = 135ms

C:\Users\Tim>

for some reason, I cant tracerout from my machine (stupid windows) as it only displays one hop. Not using VPN (obviously) nor SSL, so I have no clue what the problem is. However:

traceroute to insanelymac.com (87.124.44.2), 64 hops max, 40 byte packets

1 gatekeeper (64.200.84.2) 1.356 ms 1.182 ms 1.037 ms

2 250.ATM1-0.GW10.NYC9.ALTER.NET (63.125.96.5) 22.690 ms 22.964 ms 23.576 ms

3 545.at-6-0-0.XR2.NYC9.ALTER.NET (152.63.24.234) 22.980 ms 24.844 ms 30.361 ms

4 0.so-4-0-1.XT2.NYC9.ALTER.NET (152.63.9.90) 28.555 ms 23.219 ms 26.668 ms

5 0.so-6-0-0.XT2.NYC4.ALTER.NET (152.63.17.97) 23.265 ms 29.773 ms 29.801 ms

6 0.ae4.BR2.NYC4.ALTER.NET (152.63.3.118) 30.957 ms 28.666 ms 29.244 ms

7 204.255.168.110 (204.255.168.110) 24.353 ms 24.620 ms 24.811 ms

8 te0-3-0-5.mpd21.jfk02.atlas.cogentco.com (154.54.26.61) 30.982 ms te0-1-0-4.mpd21.jfk02.atlas.cogentco.com (154.54.31.1) 29.644 ms te0-1-0-5.mpd22.jfk02.atlas.cogentco.com (154.54.5.209) 26.508 ms

9 te0-2-0-2.mpd22.lon13.atlas.cogentco.com (154.54.42.54) 103.831 ms te0-3-0-2.mpd21.lon13.atlas.cogentco.com (154.54.45.230) 109.593 ms te0-2-0-2.mpd21.lon13.atlas.cogentco.com (154.54.44.234) 103.139 ms

10 te0-6-0-0.ccr22.lon01.atlas.cogentco.com (154.54.72.193) 111.331 ms te0-4-0-1.ccr21.lon01.atlas.cogentco.com (130.117.0.57) 101.776 ms te0-2-0-1.ccr22.lon01.atlas.cogentco.com (154.54.57.166) 114.128 ms

11 te3-2.mag01.lon01.atlas.cogentco.com (130.117.2.18) 112.136 ms te1-2.mag01.lon01.atlas.cogentco.com (130.117.3.225) 107.008 ms te2-2.mag01.lon01.atlas.cogentco.com (130.117.1.74) 393.345 ms

12 149.6.184.110 (149.6.184.110) 103.737 ms 103.468 ms 102.982 ms

13 87.124.32.94 (87.124.32.94) 102.003 ms 442.311 ms 181.704 ms

14 r1s.c2.catn.com (87.124.43.21) 105.542 ms 98.867 ms 100.354 ms

15 r1s.c2.catn.com (87.124.43.21) 98.103 ms 97.611 ms 105.405 ms

and:

87.124.44.2 is from United Kingdom(UK) in region Western Europe

TraceRoute to 87.124.44.2 [insanelymac.com]

Hop - (ms) - (ms) - (ms) - IP Address Host name

1 - 0 - 0 - 0 - 206.123.64.42 -

2 - 0 - 0 - 0 - 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net

3 - 15 - 0 - 0 - 64.125.26.213 xe-1-1-0.cr2.dfw2.us.above.net

4 - 5 - 5 - 6 - 64.125.31.122 xe-4-2-0.cr2.iah1.us.above.net

5 - 41 - 41 - 41 - 64.125.31.250 xe-5-0-0.cr2.dca2.us.above.net

6 - 107 - 107 - 106 - 64.125.24.42 xe-4-1-0.mpr1.lhr3.uk.above.net

7 - 107 - 107 - 128 - 64.125.24.122 xe-8-3-1.mpr2.lhr3.uk.above.net

8 - 107 - 107 - 143 - 64.125.28.206 xe-1-0-0.mpr1.lhr8.uk.above.net

9 - 107 - 107 - 107 - 94.31.35.219 94.31.35.219.available.above.net

10 - 112 - 109 - 109 - 87.124.32.97 -

11 - 109 - 109 - 109 - 87.124.43.21 r1s.c2.catn.com

12 - 110 - 109 - 109 - 87.124.44.2 insanelymac.com

Trace complete

from two different web tools... both in the US (one east coast, one west coast)

I noticed that Safari has a very short time-out period. Loading the same page in FireFox will get you there. Safari on windows sucks anyways, and I really prefer FireFox all around. However, its been slow for me as well. I just have a lot of patience. Or perhaps very little social life - either way I haven't been annoyed with the waiting thus far. I agree with Cat_7 above that its most likely not finding the site that is slow, its the rendering of the site once its been reached.

Hope my info helps...

instant idiot · September 6, 2012

In case it happens to be useful to anyone, here is a tracepath from someone (me ) who has not been having any problems at all with accessing this site.

tracepath insanelymac.com
1:  <removed>				 							0.159ms pmtu 1500
1:  <removed>		   								  3.399ms
1:  <removed>		   								  2.670ms
2:  73.90.28.1										   10.710ms
3:  no reply
4:  xe-2-0-1-0-ar03.troutdale.or.bverton.comcast.net	 13.521ms asymm  5
5:  pos-1-15-0-0-cr01.seattle.wa.ibone.comcast.net	   17.729ms
6:  be-12-pe03.seattle.wa.ibone.comcast.net			  15.912ms
7:  as6461.seattle.wa.ibone.comcast.net				  37.095ms asymm  8
8:  xe-0-0-0.mpr2.sea1.us.above.net					  19.733ms
9:  xe-1-2-0.cr2.ord2.us.above.net					   69.671ms asymm 11
10:  xe-0-0-0.cr1.ord2.us.above.net					   68.697ms asymm 12
11:  xe-2-1-0.cr1.lga5.us.above.net					   92.543ms asymm 13
12:  ge-2-1-0.mpr1.lhr3.uk.above.net					 205.646ms asymm 14
13:  xe-2-0-0.mpr2.lhr3.uk.above.net					 204.911ms asymm 15
14:  xe-1-0-0.mpr1.lhr8.uk.above.net					 204.789ms asymm 17
15:  94.31.35.219.available.above.net					204.295ms asymm 17
16:  87.124.32.97										204.663ms asymm 17
17:  r1s.c2.catn.com									 204.775ms asymm 18
18:  r1s.c2.catn.com									 204.793ms reached
 Resume: pmtu 1500 hops 18 back 47

instant idiot · January 24, 2013

Hm, now I am having issues. Sometimes Firefox claims "Can't find server," but usually just really long--upwards of thirty seconds--loading times. I can't detect any significant packet loss with ping, but here's a traceroute done during severely delayed loading.

traceroute to insanelymac.com (87.124.44.2), 30 hops max, 60 byte packets
1  my-router (192.168.1.1)  0.570 ms  0.772 ms  1.472 ms
2  * * *
3  te-0-2-0-1-ur04.eugene.or.bverton.comcast.net (68.85.148.121)  13.900 ms  14.084 ms  14.200 ms
4  ae-5-0-ar03.troutdale.or.bverton.comcast.net (68.87.216.121)  16.724 ms  16.622 ms  16.417 ms
5  pos-2-2-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.95.97)  21.286 ms pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.201)  22.117 ms pos-1-15-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.93.25)  21.060 ms
6  be-12-pe03.seattle.wa.ibone.comcast.net (68.86.84.106)  20.310 ms  18.929 ms  19.060 ms
7  as174.seattle.wa.ibone.comcast.net (66.208.228.110)  84.941 ms  76.536 ms  76.315 ms
8  te9-3.ccr02.sea01.atlas.cogentco.com (154.54.82.37)  163.485 ms te4-8.ccr02.sea01.atlas.cogentco.com (154.54.81.113)  161.678 ms te2-7.ccr02.sea01.atlas.cogentco.com (154.54.85.181)  161.321 ms
9  te0-7-0-4.ccr21.slc01.atlas.cogentco.com (154.54.80.10)  47.331 ms te0-0-0-4.ccr21.slc01.atlas.cogentco.com (154.54.5.34)  49.051 ms te0-7-0-10.ccr21.slc01.atlas.cogentco.com (154.54.81.61)  48.093 ms
10  te3-3.ccr02.den01.atlas.cogentco.com (154.54.3.13)  144.796 ms te4-3.ccr01.den01.atlas.cogentco.com (154.54.0.41)  48.680 ms te9-1.ccr01.den01.atlas.cogentco.com (154.54.87.17)  248.854 ms
11  te0-3-0-7.ccr21.mci01.atlas.cogentco.com (154.54.87.86)  67.177 ms te0-2-0-7.ccr21.mci01.atlas.cogentco.com (154.54.82.206)  60.892 ms  61.573 ms
12  te0-7-0-33.mpd21.ord01.atlas.cogentco.com (154.54.2.234)  74.381 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com (154.54.45.154)  73.122 ms te0-1-0-2.mpd22.ord01.atlas.cogentco.com (154.54.3.201)  68.645 ms
13  te0-3-0-6.ccr22.bos01.atlas.cogentco.com (154.54.43.198)  96.888 ms te0-3-0-1.ccr21.bos01.atlas.cogentco.com (154.54.7.82)  97.059 ms te0-3-0-6.ccr21.yyz02.atlas.cogentco.com (154.54.28.2)  93.856 ms
14  te0-3-0-5.ccr22.lpl01.atlas.cogentco.com (154.54.85.222)  157.338 ms te0-3-0-3.ccr22.ymq02.atlas.cogentco.com (154.54.25.30)  96.142 ms te0-1-0-6.ccr21.ymq02.atlas.cogentco.com (154.54.44.113)  92.153 ms
15  te0-2-0-0.ccr21.lon01.atlas.cogentco.com (154.54.57.105)  163.632 ms te0-4-0-6.ccr22.lpl01.atlas.cogentco.com (154.54.44.214)  158.706 ms te0-2-0-3.ccr22.lon13.atlas.cogentco.com (154.54.58.101)  170.858 ms
16  te0-4-0-0.ccr22.lon01.atlas.cogentco.com (130.117.0.205)  167.255 ms te0-4-0-0.ccr21.lon01.atlas.cogentco.com (130.117.0.117)  163.579 ms te0-1-0-3.ccr22.lon01.atlas.cogentco.com (154.54.74.65)  167.682 ms
17  te0-1-0-0.ccr21.lon01.atlas.cogentco.com (154.54.57.109)  168.589 ms te1-1.mag02.lon01.atlas.cogentco.com (154.54.74.110)  166.913 ms te0-4-0-6.ccr22.lon01.atlas.cogentco.com (154.54.74.57)  173.345 ms
18  te1-1.mag02.lon01.atlas.cogentco.com (154.54.74.110)  165.479 ms  165.048 ms 149.6.184.110 (149.6.184.110)  159.970 ms
19  149.6.184.110 (149.6.184.110)  164.383 ms  172.759 ms  169.472 ms
20  r1s.c2.catn.com (87.124.43.21)  169.013 ms  168.065 ms 87.124.32.94 (87.124.32.94)  174.952 ms
21  r1s.c2.catn.com (87.124.43.21)  168.988 ms  165.673 ms  165.313 ms

I've also had some "Driver Errors" as in the attached .html. While attempting to attach it:

    www.insanelymac.com Driver Error.htm

   Upload Skipped (Error IO)
   www.insanelymac.com Driver Error.htm

   Upload Skipped (Error503)
   www.insanelymac.com Driver Error.htm

   Done (uploaded 3.24 KB)

   Add to Post | Delete

www.insanelymac.com Driver Error.htm

Mr.D. · January 25, 2013

I also had that same driver issue today... strange. I had never seen that before. I restarted firefox (waterfox for me) and it seemed better. I thought it was a fire(water)fox issue but maybe it was just good(bad) timing?

Could I use(not use) any more parentheses?

instant idiot · January 25, 2013

(((I have seen the Driver Error many times before, but it had never appeared in conjunction with any other problems until now.)))

instant idiot · January 25, 2013

Problems all gone now.

*shrugs and walks away*

Kasakka · February 7, 2013

Still having issues with the site loading. This happens both at home and work so I think it's a problem on your end. Sometimes when you try to go to the site again the pages load but then a bit later (probably when the connection closes) they just go into an infinite loop.

Ed · February 7, 2013

@Kasakka please could I ask you to send me (or post here) your Traceroute and also the name of your ISP? This will massively help us track down the cause of this issue and we'll get it fixed ASAFP!

Kasakka · February 7, 2013

@Kasakka please could I ask you to send me (or post here) your Traceroute and also the name of your ISP? This will massively help us track down the cause of this issue and we'll get it fixed ASAFP!

Here you go, my ISP is TeliaSonera.


traceroute to www.insanelymac.com (87.124.44.2), 64 hops max, 72 byte packets
1  10.133.194.1 (10.133.194.1)  0.663 ms  0.483 ms  0.467 ms
2  * nblzone-gw.lau.hel.fi.nblnet.com (83.145.193.133)  1.785 ms  1.608 ms
3  pertr1-te0-3-0-5.lau.hel.fi.nblnet.com (83.145.255.246)  2.545 ms  2.458 ms  2.394 ms
4  rtr3-te7-4.lau.hel.fi.nblnet.com (188.117.15.254)  1.977 ms * *
5  te3-5.ccr01.hel03.atlas.cogentco.com (149.6.58.57)  2.236 ms  2.014 ms  1.855 ms
6  te7-8.ccr01.hel01.atlas.cogentco.com (154.54.58.17)  2.146 ms  2.052 ms  2.044 ms
7  te0-1-0-2.ccr21.sto03.atlas.cogentco.com (154.54.36.53)  9.273 ms  9.549 ms  9.390 ms
8  te0-3-0-5.ccr21.ham01.atlas.cogentco.com (154.54.38.29)  31.615 ms  31.450 ms  31.387 ms
9  te0-4-0-4.ccr21.ams03.atlas.cogentco.com (154.54.60.173)  37.089 ms  37.058 ms  47.041 ms
10  te0-5-0-0.ccr21.lon13.atlas.cogentco.com (154.54.38.58)  60.624 ms  109.787 ms  125.876 ms
11  te0-1-0-0.ccr21.lon01.atlas.cogentco.com (154.54.57.109)  113.615 ms  44.939 ms  45.069 ms
12  te1-1.mag02.lon01.atlas.cogentco.com (154.54.74.110)  57.717 ms  47.998 ms  47.871 ms
13  149.6.184.110 (149.6.184.110)  48.122 ms  48.182 ms  50.294 ms
14  87.124.32.94 (87.124.32.94)  50.502 ms  50.506 ms  50.495 ms
15  r1s.c2.catn.com (87.124.43.21)  50.503 ms  50.512 ms  50.467 ms
16  insanelymac.com (87.124.44.2)  50.810 ms  50.542 ms  50.508 ms

The traceroute seems to always complete but loading pages can sometimes hang. If I hit enter on the address bar again they sometimes load so I'm guessing the traceroute is just hammering the connection enough for it to succeed.

VirusX · July 8, 2014

I'm having connection problems these days. Sometimes it will just take forever to load/can't connect to the server anymore (especially annoying when posting a long answer) and sometimes it's super fast. No real pattern here :/

ISP is O2

traceroute to insanelymac.com (87.124.92.7), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  0.432 ms  0.236 ms  0.203 ms
 2  rdsl-krlh-de80.nw.mediaways.net (213.20.56.142)  20.345 ms  17.440 ms  18.008 ms
 3  xmws-krlh-de01-chan-20.nw.mediaways.net (62.53.220.129)  17.482 ms  17.027 ms  17.287 ms
 4  rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net (62.53.222.46)  16.833 ms  17.174 ms  17.015 ms
 5  rmwc-stgt-de01-so-2-1-0.nw.mediaways.net (62.53.1.50)  18.783 ms  18.793 ms  18.673 ms
 6  rmwc-brln-de02-xe-1-0-8.nw.mediaways.net (62.53.5.16)  32.134 ms  31.916 ms
    rmwc-brln-de02-xe-2-0-3.nw.mediaways.net (62.53.1.45)  32.999 ms
 7  rmwc-frnk-de02-chan-4-0.nw.mediaways.net (62.53.1.108)  43.609 ms  43.603 ms  74.017 ms
 8  xmwc-lond-uk01-chan-3-0.nw.mediaways.net (195.71.254.110)  110.236 ms  59.030 ms  58.639 ms
 9  linx1.thn.fubra.net (195.66.225.33)  59.378 ms  59.061 ms  58.989 ms
10  thnmch1g.virgin.cer1.mch.fubra.net (87.124.32.94)  62.453 ms  61.925 ms  62.154 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

traceroute to 81.200.64.50 (81.200.64.50), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  0.421 ms  0.236 ms  0.185 ms
 2  rdsl-krlh-de80.nw.mediaways.net (213.20.56.142)  20.730 ms  17.740 ms  17.507 ms
 3  xmws-krlh-de02-chan-20.nw.mediaways.net (62.53.220.133)  17.026 ms  16.907 ms  17.126 ms
 4  rmws-krlh-de01-gigaet-1-0-0.nw.mediaways.net (62.53.223.71)  16.808 ms  16.999 ms  17.064 ms
 5  rmwc-stgt-de01-so-2-1-0.nw.mediaways.net (62.53.1.50)  18.495 ms  18.830 ms  18.937 ms
 6  rmwc-brln-de02-xe-1-0-8.nw.mediaways.net (62.53.5.16)  34.285 ms  32.174 ms
    rmwc-brln-de02-xe-2-0-3.nw.mediaways.net (62.53.1.45)  32.082 ms
 7  rmwc-brln-de01-chan-5-0.nw.mediaways.net (62.53.1.112)  32.236 ms  53.892 ms  32.095 ms
 8  xmws-frnk-de07-chan-0.nw.mediaways.net (62.53.5.176)  42.875 ms  43.098 ms  42.984 ms
 9  te-3-4.ar2.fra4.gblx.net (80.81.192.39)  43.266 ms  43.308 ms  42.982 ms
10  nominum.port-c2.552.406.ar4.lon3.gblx.net (64.210.69.250)  60.754 ms  60.169 ms  60.969 ms
11  81.200.66.253 (81.200.66.253)  60.084 ms  60.825 ms  60.116 ms
12  advancedsearch.virginmedia.com (81.200.64.50)  60.928 ms * *

Ed · July 21, 2014

Guys, after our outage last week (which was related to this issue), things should now (hopefully) be back to normal. If not, please do let me know and post your traceroutes. Thanks and sorry for the inconvenience!

IntelFanatic · July 22, 2014

Forum is so slow for me the last days

65 packets transmitted, 0 packets received, 100.0% packet loss

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Ed · July 22, 2014

Sorry to hear that, @IntelFanatic - could you post a traceroute for me please?

IntelFanatic · July 22, 2014

@Ed

4 ht-rc0001-cr102-xe-0-0-4-0.core.as9143.net (213.51.186.30) 6.070 ms 5.992 ms 14.528 ms

5 asd-tr0610-cr101-ae4-0.core.as9143.net (213.51.158.102) 10.574 ms 10.661 ms 9.387 ms

6 ae5-125.ams29.ip4.gtt.net (77.67.64.65) 9.411 ms 10.166 ms 9.971 ms

7 xe-8-0-3.lon10.ip4.gtt.net (141.136.106.217) 18.840 ms

xe-7-0-3.lon10.ip4.gtt.net (141.136.106.213) 16.627 ms

xe-8-0-3.lon10.ip4.gtt.net (141.136.106.217) 15.360 ms

8 fubra-gw.ip4.gtt.net (77.67.65.194) 19.296 ms 24.770 ms 16.979 ms

9 igp1.cer1.thn.fubra.net (87.124.32.65) 17.700 ms 16.919 ms 18.515 ms

10 thnmch1g.virgin.cer1.mch.fubra.net (87.124.32.94) 20.061 ms 20.099 ms 23.649 ms

3 10.240.32.1 (10.240.32.1) 8.001 ms 7.575 ms 7.794 ms

4 ht-rc0001-cr102-xe-0-0-4-0.core.as9143.net (213.51.186.30) 7.501 ms 7.324 ms 7.796 ms

5 asd-tr0610-cr101-ae4-0.core.as9143.net (213.51.158.102) 9.224 ms 9.924 ms 9.806 ms

6 ix-19-0.tcore1.ad1-amsterdam.as6453.net (195.219.150.73) 9.826 ms 10.091 ms 10.373 ms

7 te4-4-10g.ar2.ams1.gblx.net (64.208.27.5) 10.421 ms 9.432 ms 9.944 ms

8 nominum.port-c2.552.406.ar4.lon3.gblx.net (64.210.69.250) 18.871 ms 17.748 ms 17.845 ms

9 81.200.66.253 (81.200.66.253) 18.354 ms 17.855 ms 18.451 ms

10 advancedsearch.virginmedia.com (81.200.64.50) 17.144 ms 17.717 ms 17.883 ms

bsancken · August 9, 2014

Agh same thing with me- 100% packet loss

$ traceroute insanelymac.com
traceroute to insanelymac.com (87.124.92.7), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  1.122 ms  0.837 ms  0.876 ms
 2  207-179-195-1.mtco.com (207.179.195.1)  35.420 ms  35.304 ms  35.231 ms
 3  marsbb1-eth-1-17.mtco.com (207.179.250.249)  36.070 ms  36.903 ms  36.198 ms
 4  chibb1-ve-207.mtco.com (207.179.253.58)  42.700 ms  37.832 ms  37.559 ms
 5  208.68.86.193 (208.68.86.193)  36.818 ms  37.134 ms  37.453 ms
 6  xe-5-1-0.er2.ord2.us.above.net (208.185.185.65)  39.944 ms  36.827 ms  39.827 ms
 7  ae15.cr2.ord2.us.above.net (64.125.24.149)  37.193 ms  41.517 ms  37.629 ms
 8  ae6.cr2.lga5.us.above.net (64.125.24.29)  57.374 ms  82.299 ms  54.249 ms
 9  ae1.cr1.lga5.us.above.net (64.125.29.37)  54.964 ms  57.332 ms  54.447 ms
10  ae3.mpr3.lhr3.uk.above.net (64.125.21.206)  127.100 ms  125.120 ms  126.680 ms
11  ae7.mpr1.lhr8.uk.above.net (64.125.21.18)  131.000 ms  128.385 ms  125.876 ms
12  94.31.35.219.available.above.net (94.31.35.219)  125.759 ms  125.135 ms  124.347 ms
13  igp1.cer2.wok.fubra.net (87.124.32.90)  125.484 ms  123.963 ms  125.962 ms
14  thnwok100m.telstra.cer2.thn.fubra.net (87.124.32.85)  126.623 ms  130.671 ms  124.360 ms
15  igp1.cer1.thn.fubra.net (87.124.32.65)  123.519 ms  127.713 ms  123.198 ms
16  thnmch1g.virgin.cer1.mch.fubra.net (87.124.32.94)  128.591 ms  127.027 ms  125.252 ms
17  * * *
18  * * *
19  * * *
20  *

insanelymac has been really hard to access for a couple off days anybody else had the same problem?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites