Skip to main content
JFrog

JFrog Cloud Platform may experience short service disruption due to planned maintenance on AWS APNE1 Tokyo region

Degraded Lasted 1h 18m · started · JFrog's page

Level
confirmed
Worst impact
Degraded
Components
Artifactory, Distribution, Pipelines
Regions
apac

What to do

  • Check whether you use JFrog Artifactory, Distribution, Pipelines in apac. 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 1h 18m it lasted.

    Anything that failed between 2024-05-05 05:12 UTC and 2024-05-05 06:30 UTC may need a replay.
  • Subscribe to JFrog's feed to hear about the next one first. RSS feed

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

Updates from JFrog 2

  1. investigating

    JFrog Cloud Platform may experience short service disruption due to planned maintenance on Tokyo (prod-apne-1) region

    provider

  2. resolved

    This incident has been resolved.

    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-228765ff11

Is JFrog still down?

No, this incident was resolved 2024-05-05 06:30 UTC. For JFrog's live state, see https://down.guide/jfrog.

How long did it last?

1h 18m, from 2024-05-05 05:12 UTC to 2024-05-05 06:30 UTC, by the times JFrog posted.

What was affected?

JFrog named Artifactory, Distribution, Pipelines in apac.

What caused it?

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

Where does this come from?

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