There seems to be almost zero information content at status.heroku.com. Does anyone have a better parser than mine? The general posting format seems to be:
posting @ t[0]: ISSUE: We are observing increased [ server | HTTP | network | database | routine] error [ rates (and | or) latencies ] to [ applications | the Heroku API ]. We are investigating and will post additional updates as we learn more. n-2 postings @ t[i]: ISSUE: We are continuing to work on resolving the [ server | HTTP | network | database | routing] issues. [ Applications are largely up | the problems are largely isolated to our <something obscure> | except for an extremely small number of requests | problems seem to be isolated to intermittent problems with <something obscure> | it's really not such a big deal at all and we can't understand why so many of you are even looking at status.heroku.com right now but we'll write something reassuring here anyway ], but we are still experiencing some performance degradation. We are working to resolve this problem as quickly as possible. nth (and final) posting hours/days later @ t[n]: We believe the incident is now entirely resolved. Error rates have returned to nominal levels. We will continue to monitor the platform and HTTP stack very closely, but at this time are discontinuing tracking of this incident. Missing are the specifics: what really happened? how bad was it? what broke? why? what fixed it? -- from a fan/customer/supporter of heroku -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
