KT Walrus Posted January 23, 2013 Share Posted January 23, 2013 Am I the only one not being able to access support today? Link to comment Share on other sites More sharing options...
AlexWright Posted January 23, 2013 Share Posted January 23, 2013 Edit: Seems to be back up. Link to comment Share on other sites More sharing options...
MarcusH Posted January 23, 2013 Share Posted January 23, 2013 same here, Client Area very slow, every other page times out. Link to comment Share on other sites More sharing options...
KT Walrus Posted January 23, 2013 Author Share Posted January 23, 2013 Must be under attack. I had just clicked on the download link to get the new IPB this morning when the site stopped responding. I still haven't been able to load any page on www.invisionpower.com so maybe they have blocked my IP? Link to comment Share on other sites More sharing options...
Management Charles Posted January 23, 2013 Management Share Posted January 23, 2013 It's not under attack we just released 3.4.2 so everyone and their mother is accessing us :) Link to comment Share on other sites More sharing options...
sunrisecc Posted January 23, 2013 Share Posted January 23, 2013 And email notifications from the tracker are now over two hours old. Link to comment Share on other sites More sharing options...
Management Charles Posted January 23, 2013 Management Share Posted January 23, 2013 And email notifications from the tracker are now over two hours old. That's just from the backlog from sending out the bulk email about the release. It is actually almost caught up so emails will be normal in less than one hour. Link to comment Share on other sites More sharing options...
sunrisecc Posted January 23, 2013 Share Posted January 23, 2013 Thank you. Charles. Link to comment Share on other sites More sharing options...
KT Walrus Posted January 23, 2013 Author Share Posted January 23, 2013 It's not under attack we just released 3.4.2 so everyone and their mother is accessing us :smile: Looks like you are using some sort of CDN for www.invisionpower.com and the node that I get has been unresponsive for 3 hours or so. Here is a dig and ping: $ dig www.invisionpower.com ; <<>> DiG 9.8.3-P1 <<>> www.invisionpower.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56470 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.invisionpower.com. IN A ;; ANSWER SECTION: www.invisionpower.com. 119 IN CNAME dc-4b452cc5.invisionpower.com. dc-4b452cc5.invisionpower.com. 119 IN A 50.28.75.102 ;; Query time: 4 msec ;; SERVER: 10.0.1.1#53(10.0.1.1) ;; WHEN: Wed Jan 23 14:59:28 2013 ;; MSG SIZE rcvd: 81 $ ping 50.28.75.102 PING 50.28.75.102 (50.28.75.102): 56 data bytes 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 ^C --- 50.28.75.102 ping statistics --- 11 packets transmitted, 0 packets received, 100.0% packet loss Link to comment Share on other sites More sharing options...
Management Charles Posted January 23, 2013 Management Share Posted January 23, 2013 That's interesting as that is not at all what I get for dig: dig invisionpower.com ; <<>> DiG 9.8.3-P1 <<>> invisionpower.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44744 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;invisionpower.com. IN A ;; ANSWER SECTION: invisionpower.com. 300 IN A 141.101.112.30 invisionpower.com. 300 IN A 190.93.243.29 invisionpower.com. 300 IN A 190.93.242.29 invisionpower.com. 300 IN A 141.101.123.30 invisionpower.com. 300 IN A 141.101.113.30 ;; Query time: 37 msec ;; SERVER: 10.1.10.1#53(10.1.10.1) ;; WHEN: Wed Jan 23 15:06:40 2013 ;; MSG SIZE rcvd: 115 Link to comment Share on other sites More sharing options...
Connor T Posted January 23, 2013 Share Posted January 23, 2013 ^ try www.invisionpower.com Its back up now. Link to comment Share on other sites More sharing options...
Leo Light Posted January 23, 2013 Share Posted January 23, 2013 It's up, it's down..etc...I'm just going to wait to upgrade..I keep getting timed out. lol Link to comment Share on other sites More sharing options...
KT Walrus Posted January 23, 2013 Author Share Posted January 23, 2013 That's interesting as that is not at all what I get for dig: You need to "dig www.invisionpower.com". It is the "www" domain that you seem to have on a CDN. I still have no connectivity to "www" and therefore cannot download the new IPB. I think your DNS for the CDN needs to recognize that the node I connect to is down and to change the DNS to use another node. I am in Northern Virginia and the CDN seems to be at LiquidWeb (traceroute below): $ traceroute www.invisionpower.com traceroute to dc-4b452cc5.invisionpower.com (50.28.75.102), 64 hops max, 52 byte packets 1 10.0.1.1 (10.0.1.1) 1.076 ms 1.297 ms 1.182 ms 2 10.5.0.1 (10.5.0.1) 11.768 ms 8.770 ms 9.961 ms 3 ip72-219-248-73.dc.dc.cox.net (72.219.248.73) 10.605 ms 9.040 ms 10.210 ms 4 ip68-100-2-29.dc.dc.cox.net (68.100.2.29) 9.935 ms 9.850 ms 9.963 ms 5 68.1.4.139 (68.1.4.139) 10.575 ms 10.298 ms 10.147 ms 6 68.105.31.202 (68.105.31.202) 11.429 ms 11.801 ms 12.295 ms 7 pos-3-13-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.86.69) 12.367 ms 11.478 ms 11.564 ms 8 he-0-10-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.10) 27.409 ms 23.791 ms 24.082 ms 9 he-0-5-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.150) 47.909 ms 47.549 ms 47.943 ms 10 be-14-pe03.350ecermak.il.ibone.comcast.net (68.86.82.210) 41.178 ms 41.291 ms 41.885 ms 11 66-208-216-86.ubr01b.mchncb01.pa.hfc.comcastbusiness.net (66.208.216.86) 37.702 ms 37.150 ms 35.797 ms 12 lw-dc2-core6-te9-2.rtr.liquidweb.com (209.59.157.226) 42.767 ms 46.989 ms 42.199 ms 13 lw-dc3-dist14.rtr.liquidweb.com (69.167.128.79) 40.935 ms 42.232 ms 42.174 ms 14 69.167.128.70 (69.167.128.70) 43.108 ms 41.880 ms 43.143 ms 15 * The traceroute hangs at "15". Link to comment Share on other sites More sharing options...
Management Charles Posted January 23, 2013 Management Share Posted January 23, 2013 Iiiiiinteresting. We're looking at it now. Send me an email if you would like me to get you 3.4.2 before we address this. Link to comment Share on other sites More sharing options...
thompsone Posted January 23, 2013 Share Posted January 23, 2013 I have a related DNS issue but it's with not receiving email notifications because there's no RDNS (either it does not exist or is incorrect). Spamdyke drops the emails for failing RDNS, I could of course whitelist Invision's domain but since this is such a basic requirement for email this may be affecting others. Addressing the problem locally is better than requesting everyone in the world whitelist *invisionpower.com, I thought I'd try to catch a snippet of the failure when someone replies to this thread so someone can give this to one of the network people. Sorry for the derail In addition looking at this from two different points. # traceroute www.invisionpower.com (from comcast business) <snip> 10 66-208-216-86.ubr01b.mchncb01.pa.hfc.comcastbusiness.net (66.208.216.86) 181.249 ms 49.628 ms 54.192 ms 11 lw-dc2-core6-te9-2.rtr.liquidweb.com (209.59.157.226) 58.596 ms 56.627 ms 55.816 ms 12 lw-dc3-dist13.rtr.liquidweb.com (69.167.128.77) 55.563 ms 58.545 ms 61.947 ms 13 infsw01.invisionpower.com (69.167.128.68) 58.997 ms 56.764 ms 55.800 ms * </snip> # traceroute www.invisionpower.com (from singlehop) <snip> 9 66-208-216-86.ubr01b.mchncb01.pa.hfc.comcastbusiness.net (66.208.216.86) 1.598 ms 1.591 ms 1.576 ms 10 lw-dc2-core6-te9-2.rtr.liquidweb.com (209.59.157.226) 205.685 ms 205.693 ms 205.907 ms 11 lw-dc3-dist14.rtr.liquidweb.com (69.167.128.79) 9.753 ms 9.729 ms 9.716 ms 12 69.167.128.70 (69.167.128.70) 7.192 ms 7.204 ms 7.192 ms * </snip> Link to comment Share on other sites More sharing options...
KT Walrus Posted January 24, 2013 Author Share Posted January 24, 2013 Iiiiiinteresting. We're looking at it now. Send me an email if you would like me to get you 3.4.2 before we address this. The CDN node is still down, but I figured out a workaround and have downloaded 3.4.2. I just set www.invisionpower.com to 141.101.112.30 in my local /etc/hosts file (which is one of the IPs for invisionpower.com). Note that with www.invisionpower.com inaccessible to me, I couldn't log into the forum (I had logged out to see if it made any difference, only to find out I couldn't log back in). Link to comment Share on other sites More sharing options...
Management Charles Posted January 24, 2013 Management Share Posted January 24, 2013 Yes we're seeing something odd with www.invisionpower.com vs invisionpower.com too. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.