Previous incidents

Postmortem:
The Microsoft Azure Networking team has finished their investigation with the following remark:
"
Appgw V2 ALL listeners utilizing keyvault are suddenly disabled during a keyvault POLL event due to MI renewal causing outage. Suddenly all traffic handled by https listeners that are associated to keyvault certs (which are fine) are set to disabled and traffic is lost.

For mitigation, try the put on the appgw again. Any new change on the appgw should resolve it. And you have d...

Templafy Hive recovered.

Templafy Hive recovered.

Monitor recovered

We found the root cause for this incident. It was a change in our own diagnostics that temporarily triggered our status monitor. There was no actual downtime, or service degradation.

Templafy Hive recovered.

Templafy Hive recovered.

Better Uptime monitor disruption, unrelated to our services. Post Mortem from Better Uptime:
"
I reached out to the team to check on the DNS incidents that you've shared, and unfortunately, it seems like there was a brief network degradation that affected a small number of users. I'm really sorry your monitors were affected, too. The team is making sure we can prevent this from happening in the future.
"

Templafy Hive recovered.

Post mortem:
An unforseen problem with our DNS provider resulted in temporary downtime for all services dependent on resolving against the https://documotor.com hostname. The issue was immediately fixed but because of DNS propagation speed some regions might have experienced longer downtime than others.

Templafy Hive recovered.