It's still broke

1+1 still equals "server unavailable" :(

This may or may not be related, I'm getting the error message to say the input cannot be parsed on every entry, even the site examples. Can anyone confirm if this is a site problem or something at my end please.

For example, the simplest maths example shows this:

I am having the same problem as George. Regardless of the input, including the examples, the input is always unrecognized on wolframalpha.com.

I noticed this yesterday evening and it continues today. Maybe it is location based because it seems like others are not seeing this problem.

No problems to report today. All seems to be functional.

I am near San Francisco CA. Same results with Firefox and Chrome. I noticed that the "Computing" animation does not show at all, the error is immediately displayed. One interesting thing is that I was briefly able to query with both Firefox and Chrome for about 1 minute, however it is now back to the same error message.I am starting to think it might be a problem with the firewall at my work because my phone works correctly when browsing directly to the site.

Using Chrome here and it has not worked this week. I just tried a second ago. This is in san diego CA. We have a bunch of T1 connections. So its interesting that nothing has been announced at all. I only created this account to say this. I do use it almost everyday to do quick multi unit calcs for work. now I'm going to have to go back to using unit translation lookup tables and a regular old HP calculator. Oh well, it was good while it lasted.

All queries through the browser-accessed website are failing in the same manner as Dustin's above. Current location: at work in Greenville, South Carolina.

However the Wolfram Alpha App on my iPhone, currently using Cell Data (not Wifi) is not having this problem. Perhaps some server-side security gone awry?

There's an issue with my work network as well. Computer queries fail. It works on my phone. Tethering computer to phone also works.

I last successfully accessed this site from work in early January. I do not know what has changed--the network or the website.

I was having the same problem too, but found something that is working for me. Instead of using:

http://www.wolframalpha.com/

I tried using HTTPS:

https://www.wolframalpha.com/

And 125 + 375 is working as well as all the random examples available.

The Wolfram|Alpha team is aware of several issues that users are experiencing due to extensive recent updates, and we are hoping to resolve things quickly. Please patiently bear with us until everything is back to normal.

In the meantime, if you’d like to provide any specific feedback about what you’re experiencing, it would always be appreciated. You can contact info@wolframalpha.com with whatever issues you are seeing, steps to reproduce, OS/browser, account information (if applicable), etc.

You can access the mobile sit by just going directly to

http://m.wolframalpha.com

So we have changed how results get pulled into W|A to be asynchronous which is the main cause of this problem. We have discovered that certain proxy services like:

https://chrome.google.com/webstore/detail/data-saver/pfmgfdlgomnbgkofeojodiodmgpgmkac/related?hl=en

https://chrome.google.com/webstore/detail/data-compression-proxy/ajfiodhbiellfpcjjedhmmmpeeaebmep?hl=en

are altering headers that our server doesn't like. So I would expect that this is a more general problem than those extensions when using proxy services or accessing the site from certain networks that utilize proxy services. But in general if your requests are getting routed through anything that is modifying headers of the requests we may have a problem.

We are still investigating the issue and seeing what we can do to address these issues from our side.