|
Post by nickthefool on Jun 30, 2015 12:28:11 GMT
I've noticed today on the "Markets" page (the one that comes up when you click "Ratesetter Info", that shows the monthly, 1yr, 3tr & 5yr rates on one page) that the total borrower offers part is wrong.
For example, the monthly market currently shows the following borrower offers:
£915.95 3.0% £53,597.79 2.9% £79,172.83 <<2.8%
However, if you view the full market, there is £24.7k on offer at 2.8%, £4.5k at 2.7% and nothing else. £79.2k is the cumulative total on offer, ie the total on offer at 2.8% or higher, when it should be 2.8% or lower.
This may or may not occur on other markets - I suspect it does, but there isn't enough unmatched borrower money on the market to warrant the grouping.
I assume this is an error in how it's being displayed or am I missing something?
|
|
locutus
Member of DD Central
Posts: 1,059
Likes: 1,622
|
Post by locutus on Jun 30, 2015 15:25:28 GMT
I just checked and it looks fine to me. Can you post screenshots?
|
|
|
Post by nickthefool on Jul 1, 2015 8:01:53 GMT
Took this yesterday. Looks fine at the moment (and probably a lot of the time) since there isn't a lot of borrower money queued. Attachment Deleted
|
|
locutus
Member of DD Central
Posts: 1,059
Likes: 1,622
|
Post by locutus on Jul 1, 2015 9:05:15 GMT
Yes, it does look like a small discrepancy. Try calling customer services and sending them the screenshot. They may not know about it.
|
|
spiral
Member of DD Central
Posts: 909
Likes: 456
|
Post by spiral on Jul 1, 2015 10:23:08 GMT
Not sure whether this is what's occurred here but I see this quite regularly.
If you have the market screen open for some time in the background and then open the detail screen, you are comparing details from 2 different periods of time. The main screen has never refreshed since it was opened but the detail screen contains the current latest available data.
|
|
|
Post by nickthefool on Jul 6, 2015 8:48:26 GMT
Just an update - I emailed Ratesetter, and they said they weren't aware of the problem, but it seems to have fixed itself as it was working properly again (last time I checked it was anyway).
|
|