Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • It's dns isn't it
    by danjc
  • Classic
    by afr0ck
  • No, IPv6
    by ghusto
  • It's always DNS.-
    by Bluestein
  • Feel like it has to be for all of this to go down at the same time.
    by bearjaws
  • Leetcode developers win again
    by bgro
  • Haven't they got some kind of new fancy ai interface they can use to fix it?
    by alienbaby
  • This is certainly a unique status page.
    by arionmiles
  • You better bet someone started their agents with a prompt "Make a salesforce clone but with 100% uptime"
    by AmazingTurtle
  • "Make a salesforce clone but with 100% uptime"

      ⎿  You've hit your session limit · resets 2:53am (48°52.6′S, 123°23.6′W Etc/GMT+8)
  /upgrade to increase your usage limit.
    by Bluestein
  • At this point OpenAI really ought to let us know when they're testing again.
    by electroweak
  • That status page is the most salesforce thing ever.

    Scroll down. >_<

    by cyberpunk
  • At least they're consistent about UX. My only complaint is that it needs more tabs.
    by santoshalper
  • Yup. No mention of outage. Even drilling down gets nothing more than "Service Disruption".
    by chrisjj
  • It lists all instances, you can drill down into each one of them, see which services are affected, and each affected service pops up the incident timeline?

    Isn't it actually amazing, and not "the most salesforce thing ever"?

    by troupo
  • I see tabs with a spinner loading infinitely, which is indeed very salesforce like
    by dgellow
  • Wow, it's almost as long as the Every UUID V4 or Every Floating Point Number pages.
    by sunrunner
  • You can click on any of the instances and then the service that is down to read the updates. It’s not 100% clear but some sort of issue with a “legacy login service”. The latest updates say a fix is rolling out.
    by chasd00
  • Cause: Legacy Salesforce login service got into a resource-exhaustion cascade.

    Fix: Rolling some unspecified fix they proved in testing out over the fleet seemingly very slowly (After their earlier attempts to roll something out faster failed).

    Details at https://status.salesforce.com/incidents/20004433

    by fhub
  • Unplanned outage timing is never good but this is really not good.

    https://www.salesforce.com/dreamforce/

    Sept 15-17

    by mergy
  • Probably not a coincidence
    by ramesh31
  • This is what happens when more than half the company is away attending the Salesforce cult-indoctrination stuff while spending all their bandwidth making customers/partners feel good.... The stuff that matters to keep the lights on gets overlooked.
    by minimeow
  • Have you tried turning it off and then on again?

    > We're no longer pursuing restarts as a path to remediation.

    Oh you have

    by raffraffraff
  • Kind of surprised they admit they're going to try restarting and see what happens. I'm sure it happens everywhere but nobody admits it.

    > We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue.

    At least it didn't fix the problem so they can actually start finding the real cause.

    > We're no longer pursuing restarts as a path to remediation.

    This is a good example of why isn't the AI they sell telling them what's wrong? Why do they need to try restarting and "see if that resolves the issue"

    by cube00
  • Despite all of the snark here, in my experience Salesforce SRE team is quite competent. The engineering challenges of running a large PaaS - not just with own apps, but with millions of customer-written apps running on it - are quite interesting, and sadly things happen. The status page makes sense to actual customers, it's the particular "pods" where a given service runs.
    by stmw