all manners of restaurant search broken as of 1 Jan 2015?
Jan 1, 2015, 10:00 am
#1
FlyerTalk Evangelist
Original Poster
Join Date: Jan 2005
Location: home = LAX
Posts: 25,933
all manners of restaurant search broken as of 1 Jan 2015?
Every dining program I have on the computer, if I do a search today on any of my saved searches, it says "no results found" and throws me to advanced search, which also fails. 
And if I try the Airline Dining app on my Android phone, it says "you must not be in the USA or you have a problem with your internet connection", but at the bottom of the screen it serves up local ads fine.
Is RN having Y2K problems 15 years late? Why this outage mess all of a sudden on 1 Jan 2015?
And if I try the Airline Dining app on my Android phone, it says "you must not be in the USA or you have a problem with your internet connection", but at the bottom of the screen it serves up local ads fine.
Is RN having Y2K problems 15 years late? Why this outage mess all of a sudden on 1 Jan 2015?
Last edited by sdsearch; Jan 1, 2015 at 10:11 am Reason: spelling
Apr 12, 2015, 2:38 pm
#3
Join Date: Jul 2001
Programs: FlyingBlue (Platinum); AA (Executive Plat); BAEC (Silver), SPG (Platinum); Hilton (Diamond)
Posts: 698
Is this broken again!??! I can't get any search to work...and I am desperately trying to top off an account with 120 miles. An iDine would be perfect if I could just find the damn restaurants.
Apr 13, 2015, 9:05 am
#4
FlyerTalk Evangelist
Join Date: Nov 2003
Location: South Florida
Programs: AA LTG (EXP), Hilton Silver (Dia), Marriott LTP (PP), SPG LTG (P) > MPG LTPP
Posts: 11,329
Aug 6, 2015, 12:54 pm
#5
FlyerTalk Evangelist
Original Poster
Join Date: Jan 2005
Location: home = LAX
Posts: 25,933
This morning for a while I was seeing an even scarier one: All restaurants in all searches I did were showing as not giving miles today or any day in the future (both in the restaurant/calendar grid view and on the individual restaurant page). But, of course, I recalled issues like the above and just waited a while, and of course now it's back to working correctly.