Last but not least: Advertising stop at the advertising marketer
Web2com forgot to renew the domain for its ad server, which resulted in some online ads not being delivered. This was reported in a blog post on Tuesday morning. Did the ad agency really miss the deadline? *Werbewoche* investigated.
Web2com, the advertising marketer belonging to Publicitas, has forgotten to extend the domain of its ad server. This can be read on the blogging site of Tom Brühwiler on Tuesday morning. Web2com's negligence meant that a large proportion of the online advertising booked could not be delivered for a whole nine days.
Did Web2com oversleep? Werbewoche wanted to know for sure and asked the Publicitas subsidiary. "There was indeed an outage on an ad server between Saturday and Monday," confirmed Christian Gartmann, Director of Marketing & Communications at Publicitas. This led to delays in the delivery of various online advertisements. However, while checking the performance on Monday morning, it was noticed that something could be wrong. Web2com then contacted its partner company 24-7 Real Media and rectified the problem. There was no question of a nine-day outage, as stated in the blog entry. Although the domain expired on June 7, it functioned normally until June 13. The affected customers were informed of the incident immediately. Solutions were proposed to them directly.
How did the outage happen in the first place? Gartmann admitted that a URL had indeed expired. However, he emphasized that Web2com had not simply neglected to extend it. Rather, a technical service provider had been given the wrong instructions internally. The incident was annoying, but: "where work is done, mistakes happen".
Did Web2com oversleep? Werbewoche wanted to know for sure and asked the Publicitas subsidiary. "There was indeed an outage on an ad server between Saturday and Monday," confirmed Christian Gartmann, Director of Marketing & Communications at Publicitas. This led to delays in the delivery of various online advertisements. However, while checking the performance on Monday morning, it was noticed that something could be wrong. Web2com then contacted its partner company 24-7 Real Media and rectified the problem. There was no question of a nine-day outage, as stated in the blog entry. Although the domain expired on June 7, it functioned normally until June 13. The affected customers were informed of the incident immediately. Solutions were proposed to them directly.
How did the outage happen in the first place? Gartmann admitted that a URL had indeed expired. However, he emphasized that Web2com had not simply neglected to extend it. Rather, a technical service provider had been given the wrong instructions internally. The incident was annoying, but: "where work is done, mistakes happen".
