Skip to main content
DigitalOcean

Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses

Degraded Lasted 2d 2h · started · DigitalOcean's page

Level
confirmed
Worst impact
Degraded
Components
Inference
Down Index
23of 100

What to do

  • Check whether you use DigitalOcean Inference. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2d 2h it lasted.

    Anything that failed between 2026-07-13 19:04 UTC and 2026-07-15 21:46 UTC may need a replay.
  • Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DigitalOcean 5

  1. identified

    We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts. Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place

    provider

  2. monitoring

    A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

    provider

  3. identified

    We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts. Our Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

    provider

  4. monitoring

    A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.

    provider

  5. resolved

    The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels. We will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-8f599465f0

Is DigitalOcean still down?

No, this incident was resolved 2026-07-15 21:46 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.

How long did it last?

2d 2h, from 2026-07-13 19:04 UTC to 2026-07-15 21:46 UTC, by the times DigitalOcean posted.

What was affected?

DigitalOcean named Inference.

What caused it?

DigitalOcean hasn't published a root cause. If it does, it shows here.

Where does this come from?

DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.