It would have been rather useful had GCP linked these (presumably linked) incidents. The first mention of cooling in the concurrent incident was at 14:39 PDT (over 5 hours after first status update, and 4 hours after the cooling incident was created)... This is what was said:
> Description: A cooling related failure in one of our buildings that hosts zone europe-west2-a for region europe-west2 is affecting multiple Cloud services.
Totally agree. I literally piped updates to diff last night to see whether GCP were actually making progress fixing anything or just spamming the same update message. Would make a useful twitter bot…
Have you tried the presence functionality described on http://pusherapp.com/docs/presence ? It doesn't cover all use cases, but for the cases it covers, we think it does a pretty great job! Disclaimer: I'm from Pusher :)
We tried nginx http_push_module before building pusher, and it was definitely one of the inspirations. I'd recommend it if you want to use long polling and are happy to maintain your own infrastructure.
It would have been rather useful had GCP linked these (presumably linked) incidents. The first mention of cooling in the concurrent incident was at 14:39 PDT (over 5 hours after first status update, and 4 hours after the cooling incident was created)... This is what was said:
> Description: A cooling related failure in one of our buildings that hosts zone europe-west2-a for region europe-west2 is affecting multiple Cloud services.