Here's some spicy new testing. Using Opera Mini, m.fuelly.com and m.fuelly.com/login.gas displays the following:

-----

Error

Failed to connect to the Internet

100

java.io.IOException: Bad DNS Address

Click here to start the connection test.

Try again.

-----

m.fuelly.com/login brings up the fuelly 404.

This is a pretty big problem if we can't connect to the Capital I "Internet"

Their "connection test" which seems to just ping an opera server, comes up with the insightful fact that I have a working network connection.

Maybe RIM is to blame, and they can't afford to let us use the Whole Internet with the big hit they took on Friday?

Okay, I updated my opera mini and did a battery-pull reset, and opera seems to be loading m.fuelly.com and m.fulley.com/login.gas fine now.

The BB browser is still not loading the site, though. This is disappointing since I personally hate the opera mini browser. But ... progress?

Also, on a completely unrelated note, the hide live preview link below the comment box is misspelled to furlly.com, so it doesn't work.

https://www.furlly.com/add/removing-live-preview.mefi

Broken, broken internets....

Thanks, fixed the live preview thing.

Another data point: Opera Mini uses a central proxy server run by Opera. So it's probably bypassing a problem with your standard network.

Same issue here on the BlackBerry Tour. I'm in the U.S. and on Verizon. The mobile site was working about a week ago. I get the same blank page, but with the vehicle description in the title page of the browser.

Interstingly, OperMini v4.2.14912 works just fine. For me at least it appears to be a problem with the built-in BlackBerry browser.

I just tweaked the mobile site so the HTML validates. I'm not sure that's the problem here, but it's worth a shot.

tried it. no dice.

did a battery pull reset.

tried it.

_worked_

Can anyone else confirm?

Heeyyyyyy... coming up okay now on the RIM browser. Looks like y'all done fixed it. :-)

This may be purely coincidence, be related to the 27 hard resets and all the cache clearing I did, or be just an outliers of user experience...

but it seems to me like that first page is loading consistently faster than it used to. Any chance you could look at validating the rest of the mobile site to see if performance can be improved on those sides as well? Not that they've been slow, just curious if there are more improvements to be found.

Cool!