User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
goosechase.com · Cloud & developer
Is Goosechase down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → goosechase.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 366 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 375 ms | 0 |
| Mon 23 | 0 | 0.0 | 296 ms | 0 |
| Tue 01 | 0 | 0.0 | 368 ms | 0 |
| Tue 03 | 0 | 0.0 | 387 ms | 0 |
| Tue 05 | 0 | 0.0 | 302 ms | 0 |
| Tue 07 | 0 | 0.0 | 331 ms | 0 |
| Tue 09 | 0 | 0.0 | 308 ms | 0 |
| Tue 11 | 0 | 0.0 | 304 ms | 0 |
| Tue 14 | 0 | 0.0 | 360 ms | 0 |
| Tue 16 | 0 | 0.0 | 310 ms | 0 |
| Tue 18 | 0 | 0.0 | 373 ms | 0 |
| Tue 20 | 0 | 0.0 | 350 ms | 0 |
| Tue 23 | 0 | 0.0 | 377 ms | 0 |
| Wed 01 | 0 | 0.0 | 386 ms | 0 |
| Wed 03 | 0 | 0.0 | 358 ms | 0 |
| Wed 05 | 0 | 0.0 | 367 ms | 0 |
| Wed 08 | 0 | 0.0 | 305 ms | 0 |
| Wed 10 | 0 | 0.0 | 2411 ms | 0 |
| Wed 12 | 0 | 0.0 | 358 ms | 0 |
| Wed 14 | 0 | 0.0 | 363 ms | 0 |
| Wed 16 | 0 | 0.0 | 308 ms | 0 |
| Wed 18 | 0 | 0.0 | 231 ms | 0 |
| Wed 21 | 0 | 0.0 | 402 ms | 0 |
| Wed 23 | 0 | 0.0 | 374 ms | 0 |
| Thu 01 | 0 | 0.0 | 392 ms | 0 |
| Thu 03 | 0 | 0.0 | 307 ms | 0 |
| Thu 05 | 0 | 0.0 | 354 ms | 0 |
| Thu 07 | 0 | 0.0 | 417 ms | 0 |
| Thu 09 | 0 | 0.0 | 344 ms | 0 |
| Thu 11 | 0 | 0.0 | 387 ms | 0 |
| Thu 13 | 0 | 0.0 | 332 ms | 0 |
| Thu 15 | 0 | 0.0 | 296 ms | 0 |
| Thu 17 | 0 | 0.0 | 334 ms | 0 |
| Thu 19 | 0 | 0.0 | 358 ms | 0 |
| Thu 22 | 0 | 0.0 | 296 ms | 0 |
| Fri 00 | 0 | 0.0 | 336 ms | 0 |
| Fri 02 | 0 | 0.0 | 484 ms | 0 |
| Fri 04 | 0 | 0.0 | 243 ms | 0 |
| Fri 06 | 0 | 0.0 | 368 ms | 0 |
| Fri 08 | 0 | 0.0 | 292 ms | 0 |
| Fri 10 | 0 | 0.0 | 282 ms | 0 |
| Fri 12 | 0 | 0.0 | 386 ms | 0 |
| Fri 14 | 0 | 0.0 | 385 ms | 0 |
| Fri 16 | 0 | 0.0 | 276 ms | 0 |
| Fri 18 | 0 | 0.0 | 287 ms | 0 |
| Fri 20 | 0 | 0.0 | 355 ms | 0 |
| Fri 22 | 0 | 0.0 | 333 ms | 0 |
| Sat 00 | 0 | 0.0 | 366 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Goosechase badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Goosechase yet. Outages of 10 minutes or more get their own page here.
Having trouble with Goosechase?
One report per service every 10 minutes from this network. No account.
Follow Goosechase
Get an email when Goosechase goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Goosechase alerts to Slack, Discord or a webhook — free.
About Goosechase
Goosechase is listed in our Cloud & developer category and checked at goosechase.com. Goosechase is an interactive experience platform that helps organizations and schools engage, educate, and activate communities through real-world and virtual experiences.
Goosechase publishes an official status page at status.goosechase.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 325 ms average, 243–386 ms range across 11 successful checks.
Questions
Is Goosechase down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Goosechase last down?
We have not recorded a public Goosechase incident since monitoring began 8 days ago.
What is Goosechase's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Goosechase respond?
325 ms on average over the last 24 hours (243–386 ms).
Does Goosechase have an official status page?
Yes, at https://status.goosechase.com.
Goosechase not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Goosechase here at once, the problem is on Goosechase's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Goosechase. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.