Insure your business

Microsoft SLA 99.95
Author: admin

January 15, 2016

Posted in Azure | |
Real life SLA and Microsoft service.

SLA level of 99.95 % uptime/availability gives following periods of potential downtime/unavailability:

  • Daily: 43.2s
  • Weekly: 5m 2.4s
  • Monthly: 21m 54.9s
  • Yearly: 4h 22m 58.5s

Link to this page:

The SLA calculator assumes a requirement of continuous uptime (i.e. 24/7 all year long) with following additional approximations (as described in the source):

  • 365.243 days per year
  • 52.178 weeks per year
  • 30.437 days per month
  • 4.348 weeks per month

2016-01-15 (8)


MS SLA, pray as you go!
Author: admin

June 15, 2015

Posted in Azure | |
Microsoft’s SLA 99.95% means
1. If you have only one server and it is down for 365/24, Microsoft will not care!
2. If you have 2 servers and duplicate and one of them failed for 365/24, Microsoft will not care!
3. It does not means your only one server will be accessible more than 364 days/ year!
Microsoft Azure SLA
Cloud Services and Virtual Machines
·         For Cloud Services, we guarantee that when you deploy two or more role instances in different fault and upgrade domains, your Internet facing roles will have external connectivity at least 99.95% of the time.
·         For all Internet facing Virtual Machines that have two or more instances deployed in the same Availability Set, we guarantee you will have external connectivity at least 99.95% of the time.

Microsoft Cloud SLA 99.9% is not real.
Author: admin

May 29, 2015

Posted in Azure | |

6 May 2015


Azure sites
Author: admin

May 4, 2015

Posted in Azure | |

Speed test from server inside that location.

Brazil South


East US


Central US


North Central US


South Central US


West US


East US 2

North Europe


West Europe


East Asia


Southeast Asia


Japan West


Japan East



How to setup DNS.
Author: admin

May 2, 2015

Posted in Azure,Cloud computing | |

According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok if they are located in different geographical regions. Same class B may still be in the same building so it is not really safe.

Another important reason, in case you have customers outside your country,is that DNS lookup faster.

Japan West to West US 385ms


Southeast Asia to East US 535ms


North Europe to East Asia 901ms

Posted in Azure,Cloud computing | |

Are you using amazon’s DNS service, Route 53? doesn’t trust their own DNS resolution service and continues to rely on a third party service provided by UltraDNS (which is a directly competing product/service to Route 53). User questions if Route 53 is good enough for Amazon ‘s DNS   [‘’]   [TTL=172800]   [‘’] (NO GLUE)   [TTL=172800]   [‘’]   [TTL=172800]   [‘’]   [TTL=172800]   [‘’]   [TTL=172800]   [‘’]   [TTL=172800]


Your DNS   [‘’]   [TTL=172800]   [‘’]   [TTL=172800]   [‘’] (NO GLUE)   [TTL=172800]   [‘’] (NO GLUE)   [TTL=172800]


or   [‘’]   [TTL=172800]   [‘’]   [TTL=172800]   [‘’] (NO GLUE)   [TTL=172800]   [‘’] (NO GLUE)   [TTL=172800]


Different class B but may be in the same building.
Do you really know how DNS works?

Next Page »