User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
gearhost.com · Cloud & developer
Is GearHost down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with GearHost.
What to try while GearHost is having problems
Estimated fix: Not enough GearHost history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → gearhost.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 14 min ago. Last stored result reached it in 188 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 153 ms | 0 |
| Tue 00 | 0 | 0.0 | 94 ms | 0 |
| Tue 02 | 0 | 0.0 | 129 ms | 0 |
| Tue 04 | 0 | 0.0 | 123 ms | 0 |
| Tue 06 | 0 | 0.0 | 158 ms | 0 |
| Tue 08 | 0 | 0.0 | 160 ms | 0 |
| Tue 10 | 0 | 0.0 | 88 ms | 0 |
| Tue 12 | 0 | 0.0 | 187 ms | 0 |
| Tue 15 | 0 | 0.0 | 106 ms | 0 |
| Tue 17 | 0 | 0.0 | 203 ms | 0 |
| Tue 19 | 0 | 0.0 | 203 ms | 0 |
| Tue 21 | 0 | 0.0 | 197 ms | 0 |
| Wed 00 | 0 | 0.0 | 198 ms | 0 |
| Wed 02 | 0 | 0.0 | 117 ms | 0 |
| Wed 04 | 0 | 0.0 | 157 ms | 0 |
| Wed 06 | 0 | 0.0 | 121 ms | 0 |
| Wed 09 | 0 | 0.0 | 150 ms | 0 |
| Wed 11 | 0 | 0.0 | 172 ms | 0 |
| Wed 13 | 0 | 0.0 | 100 ms | 0 |
| Wed 15 | 0 | 0.0 | 187 ms | 0 |
| Wed 17 | 0 | 0.0 | 180 ms | 0 |
| Wed 19 | 0 | 0.0 | 56 ms | 0 |
| Wed 22 | 0 | 0.0 | 119 ms | 0 |
| Thu 00 | 0 | 0.0 | 214 ms | 0 |
| Thu 02 | 0 | 0.0 | 171 ms | 0 |
| Thu 04 | 0 | 0.0 | 263 ms | 0 |
| Thu 06 | 0 | 0.0 | 38 ms | 0 |
| Thu 08 | 0 | 0.0 | 120 ms | 0 |
| Thu 10 | 0 | 0.0 | 215 ms | 0 |
| Thu 12 | 0 | 0.0 | 160 ms | 0 |
| Thu 14 | 0 | 0.0 | 145 ms | 0 |
| Thu 16 | 0 | 0.0 | 217 ms | 0 |
| Thu 18 | 0 | 0.0 | 109 ms | 0 |
| Thu 20 | 0 | 0.0 | 133 ms | 0 |
| Thu 22 | 0 | 0.0 | 195 ms | 0 |
| Thu 23 | 0 | 0.0 | 135 ms | 0 |
| Fri 01 | 0 | 0.0 | 140 ms | 0 |
| Fri 03 | 0 | 0.0 | 169 ms | 0 |
| Fri 05 | 0 | 0.0 | 86 ms | 0 |
| Fri 07 | 0 | 0.0 | 174 ms | 0 |
| Fri 09 | 0 | 0.0 | 139 ms | 0 |
| Fri 10 | 0 | 0.0 | 117 ms | 0 |
| Fri 11 | 0 | 0.0 | 131 ms | 0 |
| Fri 12 | 0 | 0.0 | 172 ms | 0 |
| Fri 14 | 0 | 0.0 | 122 ms | 0 |
| Fri 16 | 0 | 0.0 | 174 ms | 0 |
| Fri 18 | 0 | 0.0 | 186 ms | 0 |
| Fri 19 | 0 | 0.0 | 189 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live GearHost 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 GearHost yet. Outages of 10 minutes or more get their own page here.
Having trouble with GearHost?
One report per service every 10 minutes from this network. No account.
Follow GearHost
Get an email when GearHost goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GearHost alerts to Slack, Discord or a webhook — free.
About GearHost
We track GearHost (gearhost.com) as part of the Cloud & developer group. Your website should never depend on one server. GearHost spreads your site across multiple data centers and clouds. Built for .NET, PHP, and Node.js. Start free.
GearHost publishes an official status page at status.gearhost.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 153 ms average, 86–195 ms range across 16 successful checks.
Questions
Is GearHost down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was GearHost last down?
We have not recorded a public GearHost incident since monitoring began 7 days ago.
What is GearHost's uptime?
From our own checks: 100% over 7 days of checks.
How fast does GearHost respond?
153 ms on average over the last 24 hours (86–195 ms).
Does GearHost have an official status page?
Yes, at https://status.gearhost.com.
GearHost 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 GearHost here at once, the problem is on GearHost'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 GearHost. 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.