Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To determine whether Azure is down, check three views in order: the public Azure Status page for broad incidents, personalized Azure Service Health for events affecting your subscriptions and regions, and Resource Health for the individual resource. Then compare the reported scope and timestamps with your application telemetry. This sequence distinguishes a Microsoft platform incident from a resource-specific event, network or configuration failure, and an application-layer outage.
An empty public status page does not prove that every customer resource is healthy. Azure Service Health is personalized to your tenant and is the more useful source for subscription-specific incidents, planned maintenance, advisories and impacted resources. Resource Health adds the state and history of a particular resource, but an Available resource does not prove that the entire application works.
How do I know if Azure is down in my region?
Use the following checks, in order, when users report errors or a workload stops responding:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Start with Azure Status. Open the public, global view to see whether Microsoft has declared a broad service or regional incident. It also provides incident history and an RSS feed. The page is designed for widespread events, so no entry is not evidence that a narrow outage is not affecting your subscription. See Microsoft’s Azure Status overview.
- Open Service Health in the Azure portal. Select the relevant directory and subscription, then review Service Issues for affected services and regions, severity, scope, start and update times, status, and any mitigation guidance. Service Health is a tenant-specific view of incidents, planned maintenance and advisories. Microsoft describes it as “a personalized service in the Azure portal that helps you stay informed about issues affecting your Azure resources” (Azure Service Health FAQ, updated April 24, 2026).
- Inspect each critical resource in Resource Health. Open the resource’s health view and examine its current state, history, event category and recommended action. Check whether the event is attributed to a platform action, planned event, user action or an unplanned event.
- Correlate the evidence. Match the resource’s Azure region, service, subscription, incident start and update timestamps with your logs, synthetic tests and user symptoms. In an active Service Issue, open Impacted Resources and note whether your resource is marked Confirmed or Potential.
- Escalate when the signals do not explain the impact. Report the application or resource impact through Service Health, or open a support request when symptoms continue without a matching incident.
Azure Status, Service Health and Resource Health answer different questions
These views are complementary, not competing products. Choosing the view that matches the question prevents a false all-clear or an unnecessary incident declaration.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| View | Scope and personalization | What it tells you | Best action |
|---|---|---|---|
| Azure Status | Public and global; not tied to your tenant | Whether Microsoft is reporting a broad Azure service or regional incident; history and RSS are available | Monitor a widespread event and communicate its public status |
| Azure Service Health | Personalized to selected subscriptions, services and regions | Service Issues, planned maintenance, advisories, severity, scope, timestamps and impacted-resource information | Filter to the affected subscription and region, configure alerts, and follow incident guidance |
| Azure Resource Health | Individual resource, where that resource type provides a signal | Current state, event history, cause category and mitigation or support options | Inspect the resource, correlate with application telemetry, and request support if a platform event is implicated |
Microsoft documents the distinctions in its Service Health FAQ, Azure Status overview and Resource Health FAQ. A resource may have no Resource Health signal at all, so a status of N/A in an impacted-resource list is not an indication that the resource is healthy or unhealthy.
Step-by-step outage diagnosis
1. Capture the first observable symptoms
Record the UTC time of the first failed request, affected hostnames, HTTP or platform error codes, failing regions, subscription IDs, resource names and whether all users or only a subset are affected. Preserve a short sample of application, gateway, identity, DNS and network logs before retries overwrite the evidence. Note whether the failure is an outage, elevated latency, authentication failure, data inconsistency or a deployment regression; each points to a different branch of the investigation.
2. Check the public incident view without treating it as a verdict
Azure Status is useful for a quick, unauthenticated check during a major event. Read the incident’s affected services, regions, current state, start time and latest update rather than relying on the page headline. The public page can lag a narrow or subscription-specific event, and it can remain clear when only a particular dependency, resource family or tenant is affected. Use its history and RSS when you need to compare the current event with previous public notices.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors3. Filter Service Health to the environment that is failing
In the Azure portal, switch to the directory and subscription that own the workload. In Service Health, inspect Service Issues first, then review planned maintenance and health advisories. Verify that the event’s service and region match the workload, that the incident is active or within the observed failure window, and that the severity and scope are consistent with the symptoms. Open the incident details for the latest update and mitigation instructions. Portal labels and navigation can change, so use the current labels shown in your tenant.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
4. Use Impacted Resources to test the connection to your workload
For an active Service Issue, open the impacted-resources view and search for the resource, resource group or subscription. Confirmed means Azure reports that the resource is impacted by the service issue. Potential means the resource is not reported as impacted but could be affected because it belongs to the affected service or region. Potential is a prompt for deeper checks, not proof of an outage. The view can also show Resource Health where a signal exists; N/A means no such signal is available for that resource. Microsoft states that impacted-resource data in Azure Resource Graph is retained for 90 days; retention and portal behavior can change, so treat this as a current-documentation detail rather than a permanent guarantee. See Impacted Resources from Service issues.
5. Inspect Resource Health and its event history
Open Resource Health for every critical dependency, not only the front-end resource. Review the current state, the time range, event history, cause category and any mitigation guidance. The view can identify platform-initiated events, planned events, user actions and unplanned events. If Azure attributes the interruption to a platform event, use the support option presented in the Resource Health pane; Microsoft’s FAQ says a request can be submitted from that pane without a support agreement for an unavailable resource caused by platform events.
6. Correlate Azure timestamps with independent telemetry
Compare Service Health start and update times with load-balancer probes, application availability tests, dependency calls, database connection errors, deployment records, DNS changes, certificate events and identity-provider logs. Check whether failures occur only from one network, availability zone, client population or API operation. A matching region and time across several independent signals is stronger evidence of a platform event than any single status badge.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What do Available, Unavailable, Unknown and Degraded mean?
Available
Available means Resource Health has no known Azure-platform issue affecting that resource. It does not certify the application, its dependencies, its network path or its user experience. A web app can be Available while a bad deployment, expired certificate, misconfigured route, downstream API or authentication problem makes the application unusable.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Unavailable
Unavailable means Resource Health detected issues affecting the resource. Read the event details and history to determine whether Azure identifies a platform-initiated cause, a planned event, a user action or another category. Use the stated start time and mitigation guidance when deciding whether to roll back a change, wait for platform recovery or open support.
Unknown
Unknown means Azure stopped receiving enough information to determine the resource’s state. It is not, by itself, proof of a platform outage. Investigate monitoring-agent or control-plane communication, the resource type’s health-signal coverage, network isolation and any simultaneous subscription or authentication problem.
Degraded
Degraded is available for supported resource types and views when the resource remains partly functional but Azure detects impaired health. Determine which operations are failing and whether the application can route around the affected instance or dependency. Do not assume that degraded status has the same meaning for every resource type; use the event details for the specific resource.
What if Azure shows healthy but my application is unavailable?
A healthy public page or Available resource narrows the search; it does not end it. Work through these branches while keeping the original failure timestamps intact:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Check the application and deployment layer
- Compare the first failure with the last release, configuration change, feature-flag update, certificate rotation or secret expiration.
- Review application exceptions, dependency timeouts, thread or connection-pool exhaustion, queue depth and database errors.
- Test the failing endpoint from more than one location and with a known-good identity to separate an application defect from a client or authentication issue.
Check networking and name resolution
- Verify DNS resolution, private-endpoint and firewall rules, route tables, network security rules, proxy behavior and outbound dependencies.
- Compare a failing virtual network or region with a working one. A regional-looking symptom can be caused by a local route, peering or gateway configuration.
- Check whether only one protocol, port, API version or client network fails; that pattern is unlikely to be a general Azure regional outage.
Check dependencies and control-plane access
- Trace calls to databases, storage, messaging, identity, key management and third-party endpoints. The front-end resource may remain Available while a dependency is failing.
- Verify that operators can still authenticate to the subscription and resource. A permission or directory issue can look like an outage in the portal.
- Confirm whether the affected resource type supports Resource Health and whether its status is N/A rather than Available.
If these checks show a broad application impact but Service Health has no corresponding event, use Microsoft’s impact-report workflow. Microsoft reviews the report and, if it confirms an outage, the event appears in Service Issues: Report an impact in Azure Service Health.
How to report an impact or request support
Report an overall application or multiple-resource impact
Use the Service Health impact-report process when several resources are affected or the user-facing application is impaired and Azure could be responsible. Include the subscription, regions, services, resource identifiers, UTC start time, error samples, scope of affected users, tests already performed and the operational impact. A precise timeline lets Microsoft compare your report with platform telemetry. A report is an investigation path, not confirmation that Microsoft has declared an incident.
Open support from Resource Health
When Resource Health identifies an unavailable resource and attributes the event to a platform occurrence, follow the support action in that pane. The Resource Health FAQ documents that this route can be used without a support agreement for that platform-event scenario. For symptoms that persist but are not represented in Service Health, Microsoft’s Service Health FAQ recommends opening a support ticket and supplying the same timeline and evidence.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What to include in every escalation
- Subscription, tenant, resource IDs, resource type and Azure region
- UTC timestamps for first failure, recovery attempts and configuration changes
- Representative request IDs, error codes, status codes and correlation IDs
- Whether the impact is complete, intermittent, elevated latency or limited to a dependency
- Results from Azure Status, Service Health, Impacted Resources and Resource Health
- Relevant logs, availability-test results, deployment records and rollback actions
- Business effect and the recovery objective that is at risk
Prepare alerts before the next incident
Service Health can send alerts for service problems, planned maintenance and advisories. Configure rules for every subscription, service and region that matters, and verify that each action group reaches the people or systems responsible for response. Test the notification route and review it after organizational or subscription changes; an alert rule that targets only one subscription cannot protect workloads deployed elsewhere.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Resource Health supports Activity Log-based alerts and can connect to notification channels documented by Microsoft. For centralized tracking, Microsoft documents Service Health events through Azure Resource Graph and APIs. Use those integrations to retain incident records, correlate events with deployment systems and feed an on-call workflow, while recognizing that API fields and portal navigation are subject to change.
An alert should contain enough context to be actionable: subscription and region, affected service, event severity, status, start and update times, impacted resource list and a link to the incident. Pair platform alerts with independent synthetic tests so that an application outage is detected even when Azure has not published a matching Service Health event.
Regional failure: what recovery can and cannot be assumed
A regional incident does not automatically mean your workload will fail over. Whether recovery occurs depends on the architecture you actually deployed: replicated data, traffic management, identity and secrets, network connectivity, quotas, deployment artifacts, stateful dependencies and a tested runbook. The available evidence does not establish automatic cross-region failover for any particular workload.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Validate the resilience design
- List every component and dependency that must exist in the recovery region, including control-plane permissions and private connectivity.
- Document replication mode, data-loss tolerance, recovery time objective and recovery point objective for each stateful service.
- Confirm how traffic is redirected, how writes are fenced or reconciled, and how operators authenticate during a control-plane disruption.
- Run failover and failback exercises with measurable success criteria rather than relying on configuration diagrams.
During an active regional incident
- Follow the incident-specific mitigation guidance in Service Health.
- Protect data integrity before switching traffic; avoid independent writes to two regions unless the application explicitly supports that model.
- Use the documented runbook to promote replicas, update routing and verify dependencies in the recovery region.
- Measure recovery with real user journeys, not only resource-level availability.
- Keep an incident timeline and do not declare recovery until monitoring confirms stable operation.
For platform-initiated incidents, Microsoft notes that root-cause details may appear in Resource Health within 72 hours after Azure finds the cause. This is a conditional documentation timeframe for publishing cause information, not a promise that an outage will resolve within 72 hours; see the Azure Resource Health overview.
Common troubleshooting mistakes
- Relying only on Azure Status: the public page is intentionally high level and may not show a customer-specific or narrow resource event.
- Treating Potential as Confirmed: Potential means the resource is in an affected service or region, not that Azure has reported it as impacted.
- Calling Unknown an outage: Unknown indicates insufficient health information, so investigate signal coverage and connectivity.
- Calling Available a full application check: Resource Health covers the resource signal, not every dependency or user path.
- Waiting for a status page before testing: independent probes and application telemetry can reveal an outage before a public notice is posted.
- Assuming regional failover is automatic: failover requires a deliberately designed, populated and tested recovery path.
- Escalating without timestamps: Microsoft cannot efficiently correlate a vague report; provide UTC times, identifiers and representative errors.
Incident checklist
Keep this short checklist with the on-call runbook:
Quick Recap
- Capture UTC start time, symptoms, scope and representative errors.
- Check Azure Status, then the correct subscription’s Service Health.
- Match service, region, severity, status and incident timestamps.
- Review Impacted Resources and distinguish Confirmed, Potential and N/A.
- Inspect Resource Health history and cause category for each critical resource.
- Correlate platform signals with application, network, identity and dependency telemetry.
- Follow incident guidance, report the impact or open support with complete evidence.
- Use the tested regional-recovery runbook only if the architecture supports it.
- Continue independent synthetic monitoring until real user journeys are stable.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
