"Mizter T" wrote in message

On May 7, 9:48 pm, "Recliner" wrote:

"Colum Mylod" wrote:

As of today 7 May my Oyster journey history is showing only to 29
April ("it normally takes 48 hours for journeys to be added to your
statement") with a Entry in Notting Hill Gate £4 gobbled, to leave
£2.90 and no exit. The exit was Bank within the 2hr limit. Some
previous journeys also involving Bank as entry and exit are also
wrong. Has the station had a credit crunch?

It seems weird that my merry trips (Ladbroke Grove, White City,
KingsX, and several buses) all show but Bank is last there on the
20th despite being visited as part of all those journeys. Methinks a
puzzling phone call will need to be made. No, I didn't vault the
gates at Bank.

I'm also finding a lot of missed journeys or missing entry/exit
points in my Oyster journey history over the last few weeks. But
when I did a full check, the balance is correct. So I'm guessing
that the underlying transaction system is working properly, but the
reporting is broken.


This problem has cropped up beforehand - for whatever reason the
online journey history (via the web account) can get out of sync with
the data held on the central Oyster database. And it's the
transactions held on the central Oyster database that's the definitive
record.

If you look at the journey history on a touchscreen Tube ticket
machine (which is most of them these days) then you can see your
recent journey history - specifically the last eight or ten journeys,
depending on the type of ticket machine - and this screen will also
flag up any unresolved journeys (i.e. those that you'd get charged £4
for).

I'd be prepared to bet that if you were to do this you wouldn't find
that you'd been overcharged - in other words, the problem is with the
online journey history.

I'm wondering if it's possibly connected to the upgrade of the PAYG
system, and thus a resulting upgrade of the online journey history
system. Note that I'm not making any excuses though - it's certainly
not good enough, not least because it just ends up leaving punters
confused.

Yes, I thought it must be something like that. But given that this is
possibly a common fault, perhaps there should be an on-line warning of
potential errors, together with a simple way of reporting them?

Certainly, my first reaction was that there must have been some
expensive unresolved journeys, but it appears not. But I needed to do
some spreadsheet work to be sure.