2 ms·

It affected my ability to run commands on production applications. The fact that the status was degraded only for 'development' was, in my mind, disingenuous. P

It affected my ability to run commands on production applications. The fact that the status was degraded only for 'development' was, in my mind, disingenuous. Production should should have been orange, not green.

bgentry 13y ago
I interpreted your original comment, "Uptime has never really been Heroku's strong suit", to refer to application uptime. I guess you're actually referring to something different. AFAIK, when any other provider speaks about "uptime", they're referring to whether or not the service they're selling is up and running. For AWS, that'd be whether your instance or ELB is up and running as expected. For Heroku, it's whether your app is up and running. Issues in the control plane that affect your ability to make changes to your resources are generally outside the scope of any "service uptime" numbers you see published (unless that uptime is specific to the API/control plane). Edit: We do our best to publish info for both the service, and for its control plane. I would agree that our status site categories ("production" vs. "development") might not be the best way to label this split. Previously we used "app operations" and "tools". We may yet change it again.
- andrewvc 13y ago
  My impression was that development meant apps not in the production env. Now it's much more clear. I'd definitely change the wording.
  - dencold 13y ago
    Agreed, this was confusing to me as well, especially since there is no real concept of "development" on the heroku platform. you can't separate your dev/test apps from your production instances in heroku, they are all just treated as "production". might be helpful to clarify this on the status page at some point.
    - bgentry 13y ago
      The detailed explanation is here, linked from the status site: https://devcenter.heroku.com/articles/heroku-status#status-information https://devcenter.heroku.com/articles/heroku-status#status-i...

bgentry 13y ago

I interpreted your original comment, "Uptime has never really been Heroku's strong suit", to refer to application uptime. I guess you're actually referring to something different. AFAIK, when any other provider speaks about "uptime", they're referring to whether or not the service they're selling is up and running. For AWS, that'd be whether your instance or ELB is up and running as expected. For Heroku, it's whether your app is up and running. Issues in the control plane that affect your ability to make changes to your resources are generally outside the scope of any "service uptime" numbers you see published (unless that uptime is specific to the API/control plane). Edit: We do our best to publish info for both the service, and for its control plane. I would agree that our status site categories ("production" vs. "development") might not be the best way to label this split. Previously we used "app operations" and "tools". We may yet change it again.

andrewvc 13y ago
My impression was that development meant apps not in the production env. Now it's much more clear. I'd definitely change the wording.
- dencold 13y ago
  Agreed, this was confusing to me as well, especially since there is no real concept of "development" on the heroku platform. you can't separate your dev/test apps from your production instances in heroku, they are all just treated as "production". might be helpful to clarify this on the status page at some point.
  - bgentry 13y ago
    The detailed explanation is here, linked from the status site: https://devcenter.heroku.com/articles/heroku-status#status-information https://devcenter.heroku.com/articles/heroku-status#status-i...