User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Local
bk.com · Local
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests bk.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1184 ms · just now.
No status feed
Burger King does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 01 | 0 | 0.0 | 242 ms | 0 |
| Mon 02 | 0 | 0.0 | 354 ms | 0 |
| Mon 03 | 0 | 0.0 | 324 ms | 0 |
| Mon 04 | 0 | 0.0 | 378 ms | 0 |
| Mon 05 | 0 | 0.0 | 251 ms | 0 |
| Mon 06 | 0 | 0.0 | 1184 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Burger King yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Burger King goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Burger King alerts to Slack, Discord or a webhook — free.
Checks are succeeding and user reports are near the baseline.
If Burger King is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Burger King's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.