hi there @securiwiser-shams - thanks for that info. I do understand that this is a frustrating situation for you - the information my colleague hrishikesh posted yesterday is correct but wasn’t quite complete - they problems you have been experiencing are actually not related to any maintenance that netlify has performed - there was a large scale google outage yesterday:
The extent/complexity of what was going on yesterday wasn’t immediately apparent until the situation was resolved.
and while Netlify is a seperate service from Google, there are parts of our infrastructure that do depend on google and were affected (the same way other large companies were - Spotify, for example, was down because of this issue). So, while i know its frustrating to be unable to push any updates, the assertion that we mislead you or didnt communicate about planned maintenance isn’t actually so!
I realize that the end result for you is the same - but, i’m sure you appreciate the extra information.
Hopefully this makes you feel more inclined to trust our service once we have things working again.
So, onto that topic - seems like the fix we had suggested for you didn’t quite work, which is of course frustrating as well. This did indeed work for another customer, but we have some more things we can try.
Looking at your account, i do see that we have had no successful deploys via the CMS since yesterday.
As you don’t seem to have any error messages to report - the next thing we might suggest is to log into GitHub, and revoke access to netlify there. Then, please re-authenticate Netlify for GitHub, and that might fix things. At the moment, my working hypothesis is that there is that the CMS and our service and GitHub are not communicating correctly.
Do let us know if that does make things work, and I will ask Hrishikesh to take another look at your account if this doesn’t help when he comes on shift.
thanks again for your patience.