There are some users currently (1:50 PM GMT time) reporting that Facebook is down, via Twitter. It is not clear, however, what's happening, because there are other users reporting that Facebook works just fine for them. I have to mention that Facebook works for me quite well. Downrightnow.com, which is the website that monitors lots of services and reports if a service or another is working or not, is currently displaying Facebook as "Likely Service Disruption".
This state comes from users that reporting both on Twitter and on downrightnow that Facebook is down, while the Facebook officials didn't confirm (yet) that their service has any kind of problems.
If you want to see the progress of Facebook, just follow downrightnow.com. If you are an user of Facebook, please leave a comment telling us either if you have problems in accessing Facebook, or if works fine for you.
Showing posts with label crash. Show all posts
Showing posts with label crash. Show all posts
Tuesday, August 31, 2010
Wednesday, August 25, 2010
HootSuite say Twitter API is currently experiencing a critical issue that affects some third-party clients.
HootSuite announced on their official blog that Twitter's API is currently experiencing a critical issue, and that is the reason of which some third-party clients (including HootSuite), have some problems. They said that "Home" and "Mention" streams are currently not updating correctly, and this also affects the users of iOS and Android. Additionally, some users may also experience crashes when they try to view certain streams.
They also said that the guys from Twitter are aware of the problem, and they are working in order to fix this.
You can view the current status of Twitter's API here.
They also said that the guys from Twitter are aware of the problem, and they are working in order to fix this.
You can view the current status of Twitter's API here.
Monday, August 23, 2010
Setting up WDS between Asus WL 520GU and 520GC + WPA encryption gets the whole network into a conflict.
I've decided a few days ago that in order to improve the security of my wireless network, I should change the encryption of the network from WEP (which can be decrypted in under 60 seconds, that's proved), to WPA (which can resist even a year to a decryption attack, experts say). The reasons was that I had some doubts about the devices operating on my network, but everything is clear now (I have over 10 devices usually connected on the network).
I have two Asus routers, a WL 520GU one (with print server), and a WL 520GC one. I've written some time ago an article on how to set up WDS (or Wireless Distribution System) between them (a method of improving signal into your house for example, by setting them to operate in the same way, under the same name), which is available here (it should be applicable to almost any other models of Asus routers).
So, let's return to the problem from the title. I've changed their both encryption method to WPA, and I've let them continue working. Everything worked smooth for a few tens of minutes, than my devices were disconnected.They reconnected very fast (a few seconds), and continued working, again, for a few tens of minutes.
Then, suddenly, the entire network crashed, all devices were disconnected, and all tries to reconnect failed, as the main router (from which comes the internet connection) was refusing to give addresses to the devices requesting them. I said that it refused to give addresses, because it is practically the one doing the whole job, with the second one only repeating what it "says" to the network. As I wasn't able to receive the addresses, there was no possibility of getting into the routers in order to check the reports to see what could possibly fail like this. A restart of the routers (disconnecting their power cables) made the network start working again (this happened somewhere around 1:30 A.M. in the morning).
And they continued working until the following afternoon, when the network crashed again, creating exactly the same situation. I've searched for an update for the firmware of the routers, but there wasn't any. I've also searched to see if somebody else was having the same problem, and I found a few users reproducing quite the same situation, but the provided fixes were not helping at all.
I changed the encryption back to WEP in that afternoon, and everything has been working perfectly since then (very stable). I can't imagine what could be the problem that caused that crashes, probably that there's an incompatibility between these routers when they're operating in WDS while encrypted with WPA.
So, I repeat. If your Asus WDS crashes while secured with WPA, try changing that with WEP. Hope this helps you.
I have two Asus routers, a WL 520GU one (with print server), and a WL 520GC one. I've written some time ago an article on how to set up WDS (or Wireless Distribution System) between them (a method of improving signal into your house for example, by setting them to operate in the same way, under the same name), which is available here (it should be applicable to almost any other models of Asus routers).
So, let's return to the problem from the title. I've changed their both encryption method to WPA, and I've let them continue working. Everything worked smooth for a few tens of minutes, than my devices were disconnected.They reconnected very fast (a few seconds), and continued working, again, for a few tens of minutes.
Then, suddenly, the entire network crashed, all devices were disconnected, and all tries to reconnect failed, as the main router (from which comes the internet connection) was refusing to give addresses to the devices requesting them. I said that it refused to give addresses, because it is practically the one doing the whole job, with the second one only repeating what it "says" to the network. As I wasn't able to receive the addresses, there was no possibility of getting into the routers in order to check the reports to see what could possibly fail like this. A restart of the routers (disconnecting their power cables) made the network start working again (this happened somewhere around 1:30 A.M. in the morning).
And they continued working until the following afternoon, when the network crashed again, creating exactly the same situation. I've searched for an update for the firmware of the routers, but there wasn't any. I've also searched to see if somebody else was having the same problem, and I found a few users reproducing quite the same situation, but the provided fixes were not helping at all.
I changed the encryption back to WEP in that afternoon, and everything has been working perfectly since then (very stable). I can't imagine what could be the problem that caused that crashes, probably that there's an incompatibility between these routers when they're operating in WDS while encrypted with WPA.
So, I repeat. If your Asus WDS crashes while secured with WPA, try changing that with WEP. Hope this helps you.
Thursday, December 24, 2009
Problems with Yahoo! Messenger 10 ?
Yahoo! Messenger 10 was launched some time ago, but its problems are not yet resolved. Most of the reported problems are with the statuses, which refuses to change (and for sure, this is one of the most annoying problems). I got this problem several times, but Yahoo did not launch yet a fix for it. Other reported problems, and met by me, were with the sudden blocking of the program, and sometimes, even with the instant crashing of the program. On the last days, I really had serious issues when trying to change statuses, so that's why I decided to open this subject.
If you have problems like those mentioned before, or any other kind of problems with Yahoo!Messenger 10, please don't hesitate to leave a comment with details about it here.
Subscribe to:
Posts (Atom)