On November 20th, our XML service experienced a temporary disruption, resulting in HTTP 500 errors, which prevented users from accessing the necessary data through our platform.
In our latest release, we updated the Presentation value calculation logic. Unfortunately, this change introduced an unexpected error in the XML output processing, resulting in the service returning HTTP 500 responses.
Our monitoring system immediately detected the issue and alerted our development team.
Our specialists quickly investigated, identified the root cause, and implemented a fix.
By noon on November 20th, the XML service was fully restored and functioning normally.
We sincerely apologize for the inconvenience this incident has caused.
We understand how critical our XML services are for your daily operations, and we are committed to ensuring their stability and reliability.
To prevent similar issues in the future, we have already:
Thank you for your understanding and continued trust.
If you experience any disruptions or need support, please do not hesitate to reach out to our team.
It's 11 p.m., and you're staring at a 403 app_key required error, or weighing Open against Full…
Your product does not change, but the way people discover it does. So why would…
Building a chatbot is easy. Building one you would trust to talk to your customers…
For many retailers, e-commerce is a way to sell products directly to consumers. Adidas is…
Europe's e-commerce landscape continues to attract new competitors, and one of the latest developments comes…
At Icecat, managing, enriching, and syndicating millions of product data-sheets across thousands of global brands…