User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
guidebook.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 77 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 71 ms | 0 |
| Mon 14 | 0 | 0.0 | 26 ms | 0 |
| Mon 16 | 0 | 0.0 | 54 ms | 0 |
| Mon 19 | 0 | 0.0 | 46 ms | 0 |
| Mon 21 | 0 | 0.0 | 54 ms | 0 |
| Mon 23 | 0 | 0.0 | 28 ms | 0 |
| Tue 01 | 0 | 0.0 | 73 ms | 0 |
| Tue 03 | 0 | 0.0 | 109 ms | 0 |
| Tue 05 | 0 | 0.0 | 95 ms | 0 |
| Tue 07 | 0 | 0.0 | 62 ms | 0 |
| Tue 09 | 0 | 0.0 | 32 ms | 0 |
| Tue 11 | 0 | 0.0 | 104 ms | 0 |
| Tue 14 | 0 | 0.0 | 70 ms | 0 |
| Tue 16 | 0 | 0.0 | 66 ms | 0 |
| Tue 18 | 0 | 0.0 | 86 ms | 0 |
| Tue 20 | 0 | 0.0 | 85 ms | 0 |
| Tue 23 | 0 | 0.0 | 104 ms | 0 |
| Wed 01 | 0 | 0.0 | 148 ms | 0 |
| Wed 03 | 0 | 0.0 | 148 ms | 0 |
| Wed 05 | 0 | 0.0 | 106 ms | 0 |
| Wed 08 | 0 | 0.0 | 60 ms | 0 |
| Wed 10 | 0 | 0.0 | 107 ms | 0 |
| Wed 12 | 0 | 0.0 | 74 ms | 0 |
| Wed 14 | 0 | 0.0 | 170 ms | 0 |
| Wed 16 | 0 | 0.0 | 67 ms | 0 |
| Wed 18 | 0 | 0.0 | 78 ms | 0 |
| Wed 20 | 0 | 0.0 | 85 ms | 0 |
| Wed 22 | 0 | 0.0 | 75 ms | 0 |
| Thu 01 | 0 | 0.0 | 147 ms | 0 |
| Thu 03 | 0 | 0.0 | 118 ms | 0 |
| Thu 05 | 0 | 0.0 | 67 ms | 0 |
| Thu 07 | 0 | 0.0 | 92 ms | 0 |
| Thu 09 | 0 | 0.0 | 62 ms | 0 |
| Thu 11 | 0 | 0.0 | 40 ms | 0 |
| Thu 13 | 0 | 0.0 | 133 ms | 0 |
| Thu 15 | 0 | 0.0 | 228 ms | 0 |
| Thu 17 | 0 | 0.0 | 229 ms | 0 |
| Thu 19 | 0 | 0.0 | 74 ms | 0 |
| Thu 21 | 0 | 0.0 | 52 ms | 0 |
| Thu 23 | 0 | 0.0 | 71 ms | 0 |
| Fri 01 | 0 | 0.0 | 91 ms | 0 |
| Fri 03 | 0 | 0.0 | 71 ms | 0 |
| Fri 05 | 0 | 0.0 | 38 ms | 0 |
| Fri 08 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 67 ms | 0 |
| Fri 12 | 0 | 0.0 | 103 ms | 0 |
| Fri 14 | 0 | 0.0 | 36 ms | 0 |
| Fri 16 | 0 | 0.0 | 77 ms | 0 |
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.
No outages on record for Guidebook 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 Guidebook goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Guidebook alerts to Slack, Discord or a webhook — free.
We track Guidebook (guidebook.com) as part of the Cloud & developer group. Run orientation, admissions events, campus tours, and student engagement on one branded app. Guidebook powers events and everyday campus life for higher ed.
Guidebook publishes an official status page at status.guidebook.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 69 ms average, 36–103 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Guidebook incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
69 ms on average over the last 24 hours (36–103 ms).
Yes, at https://status.guidebook.com.
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 Guidebook here at once, the problem is on Guidebook'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 Guidebook. 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.