GitHub's services keep getting into incidents pretty regularly, but an outage that lasts for 6 hours is rare but not unheard of.
Past incidents:
https://www.githubstatus.com/history
The market resolves YES if any of the incidents after the creation of the market last for more than 6 hours. The incident timeline is the timestamp displayed below the incident item, otherwise resolves NO.
🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ1,337 | |
| 2 | Ṁ40 | |
| 3 | Ṁ25 | |
| 4 | Ṁ19 | |
| 5 | Ṁ16 |
resolving YES because an incident lasted for 6 hours 4 minutes.
https://www.githubstatus.com/incidents/rcnl10p4hywg
@sacredSatan we're just going back and forth, so I've opened limit orders if you want to fill them
@PatMyron wish I had taken you up on this but didn't have enough mana, and I was just looking to close this market out on 1st May, I'd stopped visiting manifold xD
After the market creation they had one incident that lasted for 4 hours and 42 minutes, and April also has had their first incident. This is just inevitable when it comes to GitHub.
https://www.githubstatus.com/incidents/z3c6q056q332
@YonatanCale just asked it because it bit me today. They had major outage across services. Added the 6 hour condition to make it more interesting but I have faith that GitHub will always have incidents spread throughout the months. Look at their recent history.
Example of an incident that lasted for 35 minutes, I'll basically consider the time between the "investingating" announcement to the "resolved" announcement. These are the timestams displayed in the list view on the history page as well.
https://www.githubstatus.com/incidents/zf2tk6x40gmh