That is about right; I have been getting 48+ hour departure reminder in the last couple of days. :confused:

Ah, that explains it. I was wondering why I got an email telling me my flights had changed, when everything was identical. it was a downgauge from an A320 to an A319.

I had earlier gotten a change email for that same itinerary, but at least that was a flight number change (same time, though).

Just got my 48-hour alert that my flight is on-time. Guess UA is very confident these days!

I've had three reminders this week for flights on time - all between 48 and 72 hours out...

Are they Nuts!
 

I got a call at 6:00 AM today, Sunday, for a 6:00 AM flight on Wedensday the 7th. As far as I can see, they changed nothing. It scared my Wife she thought it was concerning her 89 Y.O. sick Mother.

I would rather have aggressive than nothing at all. Got my first Easy Update in months today! They must have finally fixed something. I atually got two, one with a schedule change that had the new time blank (there actually was no change) and one for a UDU.

Getting calls every night this long weekend for a flight that leaves at noon Tuesday. Sigh.

I disabled easy update now.

More change I don't like.

Twice this week I've been called half an hour before my alarm goes off in the morning to let me know my flight is on time. Sigh. I e-mailed 1KVoice. I see I'm not the first, but I'm curious to see what (if anything) the response will be.

The Bomb Stikes Out Again
 

I had a flight booked UA 835 ORD - PVG on Mon 09/05 about a month out. On Thurs 09/03 at about 0230 I got a text message that says US 835 departs on time 09/05. Never have I ever received an on time notice two days before departure. Then looking at my desketop the next day I get an Easy Update that had the banner of "TIME CHANGE FOR YOUR FLIGHT: but the time listed was exactly the same time as originally booked. I thought that both messages were kind of bizzare--sure enough--


When I went to check in the attendant had a very puzzled look and after clicking away for about five minutes she said that there has been a change of equipment and that I had been re-assigned from 18H (asile) to 22B (middle) but that she mananged to get me into 28H (aisle)--upgrade still waitlisted.

When I got to the gate, I was confirmed to 8D.

When boarding I discovered that the different equipmet was a newly configured 777--good news.

Bottom line was that the EZ notice was totally mislabled as "Time has Been Canaged" when it should hae been labled as equipment change.

The exact same thing happened on my retrun on PVG-ORD.


So bottom line is that if you get a "Time Change" notice figure that it is an equipment change and that your seat assignment will be changed in the process.

Another change that I am sure you will like Sort of like a fox hunt.

This thread discusses the early Easy Update messages: http://www.flyertalk.com/forum/unite...asyupdate.html

I wouldn't always assume that there's been an change of eq. I had a couple of those messages, and nothing changed.

Talk about over agressive...
 

I just got an easy update for a flight today - 9/12 that definately not mine nor anyone else's that I know...

ez update
 

You can customize ez update not to call in the middle of the night.

This was the 1K desks response to me as well when I notified them of the issue. The problem is that I WANT to be notified in the middle of the night if there is a material change to one of my reservations. I love how the touted answer to a clearly dysfunctional product is for the customer to fix it.

Their website is rubbish, the notifications are a variable, in fact the only conclusion that any sane person can come to is that their entire IT from top to bottom is totally unfit for purpose. Presumably it will be blamed on the merger. Out of curiosity does anyone happen to know if it is outsourced ? That seems to be a feature of crap IT these days.

the problem is the only updates I was getter were for non-events but received no email or call for the two delayed flights.

thankfully someone seems to have fixed the glitch.