Page 2 of 2

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Sat Jun 17, 2017 7:12 am
by pgbennett
It looks like it has been resolved now, I now have 20 days of listings and the anomalies I had noticed before are gone.

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Wed Jun 21, 2017 8:08 am
by gtb
Now that the disruption has been resolved, is it possible to post the full RFO?

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Wed Jun 21, 2017 2:33 pm
by rkulagow
I have asked Gracenote for any information that they can share.

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Wed Jun 21, 2017 2:46 pm
by gtb
rkulagow wrote:I have asked Gracenote for any information that they can share.

Thanks. I will understand if Gracenote wants the information to be distributed only to actual licensees (Schedules Direct) who have every right to know, and not passed to the masses (who may be interested, but do not have an actual direct contractual relationship).

AWS and Google (to name two) tend to produce fairly good RFOs, which are upfront about documenting the "whoops", and the steps they will be taking to avoid that particular issue again (sometimes better monitoring, sometimes less aggressive timers in various components), sufficient so that we can be somewhat assured they believe they understand what happened and why it should not happen again (at least in that particular way).

Here's to hoping Gracenote will choose those examples of good sharing.