3 ms·
Even though the status page shows all green checkmarks, we are still experiencing issues. The web interface is showing stale data and we can't perform merges in
by yarcob 6y ago
Even though the status page shows all green checkmarks, we are still experiencing issues. The web interface is showing stale data and we can't perform merges in git.
Looks like some of their systems got out of sync and they aren't done resynchronising yet.
- yarcob 6y agoUpdate: After nothing happened, I rewrote the last commit and force pushed to trigger an update. That seemed to do the trick. I have no inside knowledge, but from the outside it looks like whatever outage they had broke the propagation of commit data from the git repo to to their MySQL database. Maybe they use webhooks for their internal systems as well? That would explain why they first saw issues with webhooks, and later issues with pull requests that might depend on them. It also looks like after they fixed the issue, they didn't replay the failed notifications. That's why I saw stale data even after they apparently fixed the issue. Then my push to the repo seemed to trigger an update, and now it's back in sync. I'm curious to hear what really happened, but I doubt this incident is important enough to anyone to warrant a detailed blog post.
- faitswulff 6y agoAfter seeing this happen over and over again, I wonder if status pages should even be run by their own parent companies.
- robbyt 6y agoSounds like Azure... Solid 500s from API, but status is green.
- eurasiantiger 6y agoI assume you’re on the lowest tiers; HTTP 500 randomly for hours seems to be the Azure way of upselling.
- viraptor 6y agoWhat's the path from random 500 for hours from a services and decision to give them more money? That seems backwards.
- square_usual 6y agoSales team uses downtime to upsell a plan with better SLAs.
- vasachi 6y agoI don’t see the logic here. “Our thing doesn’t work, pay us more, so that it still doesn’t work, but we are kinda responsible for that then”?