The issue was on our end. During last week’s planned move to a new database provider, everything went smoothly. But we didn’t allocate enough memory for the database, which is why the problem didn’t appear until Sunday night (prime time).
So it was human error basically, not a system failure.
The move was planned a year ago when we realized we’d outgrown our original provider. We have always placed snipes from multiple locations, but from a central database. Now, the database itself is multi-regional.
Thank you for bringing this to our attention.
bidslammer