Web Application Experiencing Service Disruption (404 Errors)

Update timeline

1. investigating Dec 08, 2025, 04:26 PM UTC

   We are currently investigating an issue affecting our web application hosted on Google Cloud Run. Users may be experiencing difficulties accessing certain parts of the application, manifesting as HTTP 404 errors and "ChunkLoadError" messages in their browsers. This is due to the service failing to load essential static JavaScript assets. Our engineering team has been alerted and is actively working to identify the root cause and implement a fix. We apologize for any inconvenience this may be causing and will provide an update as soon as more information is available.

2. identified Dec 08, 2025, 06:45 PM UTC

   We are currently investigating an issue where static JavaScript assets requested via https://app.mayan.co/_next/static/... are returning HTTP 404, causing intermittent page load failures and ChunkLoadError messages._ Impact Affects users accessing the app via https://app.mayan.co. Some pages may fail to load correctly or appear broken due to missing client-side chunks. The underlying application container on Cloud Run is healthy and serves these assets correctly when accessed directly. What we know The same assets return 200 OK when requested directly from the Cloud Run service URL (https://webapp-...us-central1.run.app/_next/static/...). This confirms: The application build and container image are correct. Static assets are present and served properly by the app. The 404s only occur via the public domain app.mayan.co, indicating an issue in the routing or proxy layer between app.mayan.co and Cloud Run (e.g., load balancer / CDN / path rules), not in the application code or build._ Current focus Reviewing load balancer / CDN configuration for app.mayan.co to ensure: All /_next/* paths are forwarded unchanged to the Cloud Run backend. No path rules, URL normalization, or caching policies are causing these specific static asset requests to be dropped or misrouted.*_ Next update We will provide another update once we have adjusted the routing configuration and confirmed that static asset requests to https://app.mayan.co/_next/static/... return 200 consistently.

3. monitoring Dec 08, 2025, 07:27 PM UTC

   Earlier today, some users accessing app.mayan.co experienced page load failures and ChunkLoadError messages due to 404 responses on static JavaScript assets under /_next/static/...._ Impact Affected users saw broken or partially loaded pages. The underlying Cloud Run service and application container were healthy and serving static assets correctly; the failures occurred only when traffic was routed via app.mayan.co. Root Cause The issue was traced to the hosting/routing layer in front of Cloud Run. Requests to /_next/static/... were not consistently forwarded from app.mayan.co to the Cloud Run service, resulting in 404s at the edge even though the assets were present and served correctly by Cloud Run._ Resolution We have bypassed Firebase Hosting and now route app.mayan.co directly to the Cloud Run custom domain. With this change, static asset requests are reaching the same Cloud Run service that we have verified serves all _next/static/... assets with 200 responses. Application behavior has returned to normal, and the affected routes are loading successfully._ Current Status The fix is deployed and we are monitoring the service for any recurrence or residual DNS/cache effects.

4. resolved Dec 08, 2025, 11:01 PM UTC

   The earlier issue causing 404 errors for static JavaScript assets and resulting page load failures on app.mayan.co has been fully resolved. Traffic for app.mayan.co is now routed directly to the Cloud Run custom domain, bypassing the misconfigured hosting layer that was dropping /_next/static/... requests. The Cloud Run service has been verified to serve all static assets correctly, and affected pages are loading normally. We have observed stable behavior since the change with no further errors.