# Why do I still still Resizer v1 requests, after migrating to Resizer v2?

Source: https://docs.arcxp.com/en/knowledge-articles/photo-center/why-do-i-still-still-resizer-v1-requests,-after-migrating-to-resizer-v2-.html

## Question

Why do I still still Resizer v1 requests, after migrating to Resizer v2?

## Answer

After migrating to Resizer v2, it’s normal to still see some Resizer v1 requests. This can happen for several reasons: 

- Search engines may have indexed v1 image URLs, which take time to update.
- The migration process may have missed some v1 image URLs.
- V1 images have a one-year cache (TTL). Arc XP is not clearing this cache as part of v1 deprecation, so those URLs can continue serving from cache for up to a year. After that, they’ll redirect to Resizer v2.

Additionally, some URL types are exempt from v1 deprecation and will continue using v1 until Arc upgrades them:

- Arc XP Native Specification (ANS) URLs (paths including _arc-anglerfish-_ or _arc-photo-_)
- Video thumbnail URLs (paths including _arc-goldfish-_\-thumbnails\*)
- URLs used by Queryly

## More information

- [Resizer v1 to v2 redirects](https://dev.arcxp.com/photo-center/image-resizer/resizer-v1-to-v2-redirects/)