{"action":"opened","issue":{"url":"https://api.github.com/repos/StoryShop/storyshop-status/issues/6","repository_url":"https://api.github.com/repos/StoryShop/storyshop-status","labels_url":"https://api.github.com/repos/StoryShop/storyshop-status/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/StoryShop/storyshop-status/issues/6/comments","events_url":"https://api.github.com/repos/StoryShop/storyshop-status/issues/6/events","html_url":"https://github.com/StoryShop/storyshop-status/issues/6","id":158824695,"number":6,"title":"Major outage persists, though it appears we're not alone.","user":{"login":"sethmerrick","id":664681,"avatar_url":"https://avatars.githubusercontent.com/u/664681?v=3","gravatar_id":"","url":"https://api.github.com/users/sethmerrick","html_url":"https://github.com/sethmerrick","followers_url":"https://api.github.com/users/sethmerrick/followers","following_url":"https://api.github.com/users/sethmerrick/following{/other_user}","gists_url":"https://api.github.com/users/sethmerrick/gists{/gist_id}","starred_url":"https://api.github.com/users/sethmerrick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sethmerrick/subscriptions","organizations_url":"https://api.github.com/users/sethmerrick/orgs","repos_url":"https://api.github.com/users/sethmerrick/repos","events_url":"https://api.github.com/users/sethmerrick/events{/privacy}","received_events_url":"https://api.github.com/users/sethmerrick/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/StoryShop/storyshop-status/labels/App","name":"App","color":"171717"},{"url":"https://api.github.com/repos/StoryShop/storyshop-status/labels/major%20outage","name":"major outage","color":"FF4D4D"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-07T03:01:09Z","updated_at":"2016-06-07T03:01:09Z","closed_at":null,"body":"As of ~10:45pm EST Monday, June 6, StoryShop is still suffering a complete outage. All traffic is now redirected to a simple landing page with links to the status and feedback sites.\r\n\r\nThough the issue is not yet resolved, we have learned from the team at our cloud database service provider that at the root of our sudden and unexpected problems is a newly-discovered bug in recent releases of the Node.js driver for MongoDB.\r\n\r\nFor those interested in learning more, or in seeing what the real underbelly of engineering at the bleeding edge of web technology looks like, please refer to the following tickets currently being investigated by the core team at MongoDB: \r\n\r\nhttps://jira.mongodb.org/browse/NODE-719\r\nhttps://jira.mongodb.org/browse/NODE-722\r\n\r\nAs far as we can tell, this bug has been lurking in the shadows for the past week or so, and our small development team had not yet placed sufficient load on the system to cause the results we saw immediately once the strain was multiplied by several orders of magnitude when we opened to our beta testers.\r\n\r\nIn honor of the mad whirlwind we've found ourselves swept up in over the past few days, here is a link to an image of the first documented software bug - a moth found inside the Harvard Mark II electromechanical computer in 1947: https://en.wikipedia.org/wiki/Software_bug#/media/File:H96566k.jpg\r\n\r\nHang in there brave new StoryShoppers, the end is in sight... and in the end, the beginning!\r\n\r\n-Seth"}}
{"actor":{"display_login":"sethmerrick"}}