Bing not reading sitemap index correctly for correct sitemap

I understand why this doesn't make sense from your side, Dana STAMATOIU.

If sitemap.xml is the sitemap you submitted, it contains only the four expected child sitemaps, and other tools can parse it correctly, seeing Bing attempt completely different locations such as sitemap.xml.gz would understandably make you question where Bing is getting those URLs from.

One notable point is that Bing Webmaster Tools does not obtain every sitemap URL solely from the sitemap index you submitted. Microsoft states that its Sitemaps section can contain both submitted and organically discovered sitemaps. So Bing might not find that location inside your sitemap.xml, but instead retained it separately.

That said, it doesn't account for Bing failing to correctly process the sitemap index itself while other parsers read it without a problem. As you've already established that the index is valid with other tools, I don't think repeatedly changing or resubmitting a correctly generated sitemap is particularly useful.

Since Microsoft Q&A is just a user-to-user community, contributors here do not have access to Bing's crawler/backend data to determine how Bing processed your domain. If what Bing reports in Sitemaps does not correspond at all with what actually present in your sitemap index, this really needs to be investigated by Bing Webmaster Support:

• Visit Webmaster Support - Bing Webmaster Tools
• Click Raise support request and wait for the team to connect.

Note: If you encounter AI loop when requesting support, a community member has shared a workaround (although not 100% guaranteed). By explicitly requesting a human engineer and mentioning this is an urgent issue in the text, they were able to receive a genuine UCM ticket assigned to a Global Support Webmaster Engineer.

When raising the case, consider including the actual sitemap.xml, a screenshot of what Bing Webmaster Tools > Sitemaps reports for it, and the server-log entries showing Bingbot requesting the unexpected locations. That should make the discrepancy clear without requiring you to prove again that other sitemap parsers can read the file correctly.