Accepted Adobe Stock asset returns “Page Not Found” in Indonesia and US, but works in UK and Canada

URGENT: Persistent Public Asset Accessibility Issue — Accepted Asset Returns “Page Not Found” in Indonesia and the US

Dear Adobe Stock Contributor Community and Adobe Support Team,

I am requesting further investigation into a persistent public asset accessibility issue affecting my Adobe Stock portfolio. Although my previous support requests have been marked as Resolved, the issue remains reproducible, including with a newly accepted asset.

1. Asset Information

• File ID: 2222905016

• Title: External Keyboard and Laptop for Digital Interface Review

• Upload Date: October 13, 2026

• Contributor Status: Accepted

2. Regional URL Test Results

I tested the public asset page using the following regional Adobe Stock URLs:

Indonesia — Page Not Found
https://stock.adobe.com/id/stock-photo/id/2222905016

United States — Page Not Found
https://stock.adobe.com/us/stock-photo/id/2222905016

United Kingdom — Accessible
https://stock.adobe.com/uk/stock-photo/id/2222905016

Canada — Accessible
https://stock.adobe.com/ca/stock-photo/id/2222905016

The results indicate inconsistent accessibility across regional Adobe Stock URLs. The same accepted asset is accessible through the UK and Canadian URLs but returns “Page Not Found” through the Indonesian and US URLs.

3. Previous Support History

I previously contacted Adobe Contributor Support regarding public asset pages returning “Page Not Found.” My previous support requests were marked as Resolved; however, the issue remains reproducible based on my latest tests.

I am raising this issue with the Adobe Stock Contributor Community to seek further technical guidance and determine the appropriate escalation process.

4. Portfolio Impact

My Adobe Stock portfolio currently has 69 accepted assets. I am concerned that inconsistent accessibility of public asset pages could affect the discoverability of my work and prevent potential customers in certain regions from accessing my accepted content.

The latest test provides a new example involving an accepted asset, suggesting that the issue may not be limited to previously uploaded content.

5. Request for Urgent Technical Investigation

I respectfully request assistance from an Adobe representative or Community Expert in clarifying the following:

1. Why does the same accepted asset return “Page Not Found” through certain regional URLs while remaining accessible through others?

2. Could this issue be related to regional indexing, asset publication, URL routing, or another technical component?

3. How can this issue be escalated to the appropriate technical team when previous support requests have been marked as Resolved, but the reported behavior remains reproducible?

4. What additional evidence or diagnostic information is required to identify the underlying cause?

I would appreciate a substantive technical assessment, clear guidance on the appropriate escalation process, and confirmation of the steps required to resolve this issue.

I can provide screenshots and additional test results to support the investigation.

Thank you for your attention to this matter. I look forward to your response and a clear resolution.

Kind regards,
Claresta Edawaluya Yoshuara