CheckUpstream does not yet run an independent probe against Azure Service Bus, so no availability figure is published for it — only Azure Service Bus's own disclosure record below. Azure publishes its status as an RSS feed with no per-service breakdown, so incidents shown here are Azure-wide rather than specific to this product. We do not guess which product an Azure incident touched. 3 incidents were recorded in the past 12 months; the most recent resolved 4 days ago after 15 minutes. Status signals are polled from Azure Service Bus's official status feed, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Azure Service Bus yet, so we publish no availability figure for it. What follows is Azure Service Bus's own disclosure record, which is a different thing.
Vendor disclosed: 3 incidents · 29 of 30 days with none posted · 38m of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by Azure Service Bus
7d
99.894%
30d
99.912%
90d
99.971%
180d
99.985%
1y
99.993%
Downtime like this can be refundable
If you're a paying Azure Service Bus customer, outages in these windows may count against Azure Service Bus's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Azure Service Bus entitlement →Does Azure Service Bus actually matter to you?
A Azure Service Bus outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 28, 06:19 UTC · resolved in 15m · Resolved
Aug 25, 04:03 UTC · resolved in 17m · Resolved
Aug 14, 05:28 UTC · resolved in 22m · Resolved
Live Azure Service Bus status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/azure-service-bus)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Azure Service Bus is currently Operational. CheckUpstream tracks Azure Service Bus in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Azure Service Bus down" view? See the Azure Service Bus Live status page.
Azure Service Bus's last resolved incident started 4 days ago and lasted 15 minutes (a partial outage).
We don't publish one. CheckUpstream runs no independent probe against Azure Service Bus yet, and the only other figure available would be derived from Azure Service Bus's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Azure Service Bus to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Azure Service Bus's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.