codegen.plasmic.app Loader API returning 499 since 13:08 UTC — all pages down

Issues
1

We are experiencing a complete outage on our production website since 2026-03-20 13:08 UTC due to the Plasmic Loader API returning HTTP 499 errors.

Details:

  • Endpoint: codegen.plasmic.app/api/v1/loader/html/published

  • Project ID: 2n8MyPLXPiRCEU2BD1atD4

  • Error: HTTP 499 — "Request to upstream failed in another process"

  • Impact: 100% of pages on verifymyage.de and verifymyage.co.uk are returning HTTP 500

  • Duration: 3+ hours and counting

  • Status page: https://plasmic.instatus.com shows “Operational” but the Loader API is not working

What we’re seeing in our server logs (continuously):

Error: Error parsing JSON response: SyntaxError: Unexpected token 'R', "Request to"... is not valid JSON;
status: 499; response: Request to upstream failed in another process
    at Api.<anonymous> (/app/node_modules/@plasmicapp/loader-fetcher/dist/index.js:162:15)

What we’ve verified:

  • The Plasmic CMS API (studio.plasmic.app) is working fine (HTTP 200)

  • Network connectivity from our pods to codegen.plasmic.app is OK (we can reach the host)

  • The issue is specifically the Loader/Codegen upstream returning 499 instead of JSON

  • No changes were made on our side — the transition from working to broken happened within 400ms

Library version: @plasmicapp/loader-nextjs: ^1.0.357

Could you please investigate the upstream issue on codegen.plasmic.app? This is a production outage affecting our customers.

Thank you.

2

Hello @vitor_schiavo Can you confirm if the issue has resolved?

3

Yes, issue resolved, thanks for asking.

4

But I don’t know how it started working again.

5

We received reports of loader/codegen API instability during the past few days, but our team have fixed the issue. The API should be stable now.