Skip to main content

Azure Status - Real time information about Azure Services Health Status

By
Last week I had the opportunity to talk with some people that started to take into consideration cloud and Microsoft Azure.
Even if the services and SLA’s were very clear for them, there was a thing that was not clear from them:
How can I know when a service offered by Azure is down? How can I know if the SLA is respected or not (99.9X %)?
They thought that Microsoft is the same as 10 years ago and they don’t share with customers this kind of information.
For them it was a surprise to discover the Current Health Azure Dashboard aka Azure Status and how easy you can see the status of all the services around the globe. In real time you can see the status of each services from all datacenter that are available.
On top of this, on this dashboard you have a History section that can be used to see what services had issues and what was the cause. In this way, all the clients around the world can know exactly what happen when a specific service was down.
Hint: There is a RSS feed for each service. You can use it to integrate this status on your own system/aggregator.
Additional to this portal, customer should know that if an issue of one of Azure services is affecting their services, they are usually notify by support team as soon as possible via email.
If you want to know exactly what is the SLA for different Azure services you should check the following page http://azure.microsoft.com/en-us/support/legal/sla/. On this page there are listed all the SLA for all available services. Even if you are a small customer, you will have the same SLA like the big ones. In this moment there are 2 services available that has 4 nines (99.99%) – Traffic Manager and Storage.
Another sources of Azure Status (that are not provided by Microsoft, but aggregates information from Azure services) are:


Unfortunately, in this moment you will not be able to find a portal that can gives you the uptime history for different Azure services. For example in the last 12 month the uptime for Y service was 99.999%.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more