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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

Azure AD and AWS Cognito side-by-side

By
In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more