User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
fountain.com · Cloud & developer
Is Fountain 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 Fountain.
What to try while Fountain is having problems
Estimated fix: Not enough Fountain history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 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 → fountain.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 31 min ago. Last stored result reached it in 49 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 21 | 0 | 0.0 | 208 ms | 0 |
| Mon 23 | 0 | 0.0 | 151 ms | 0 |
| Tue 01 | 0 | 0.0 | 172 ms | 0 |
| Tue 03 | 0 | 0.0 | 148 ms | 0 |
| Tue 05 | 0 | 0.0 | 181 ms | 0 |
| Tue 07 | 0 | 0.0 | 108 ms | 0 |
| Tue 09 | 0 | 0.0 | 206 ms | 0 |
| Tue 11 | 0 | 0.0 | 144 ms | 0 |
| Tue 14 | 0 | 0.0 | 117 ms | 0 |
| Tue 16 | 0 | 0.0 | 227 ms | 0 |
| Tue 18 | 0 | 0.0 | 181 ms | 0 |
| Tue 20 | 0 | 0.0 | 254 ms | 0 |
| Tue 23 | 0 | 0.0 | 74 ms | 0 |
| Wed 01 | 0 | 0.0 | 262 ms | 0 |
| Wed 03 | 0 | 0.0 | 219 ms | 0 |
| Wed 05 | 0 | 0.0 | 227 ms | 0 |
| Wed 08 | 0 | 0.0 | 173 ms | 0 |
| Wed 10 | 0 | 0.0 | 196 ms | 0 |
| Wed 12 | 0 | 0.0 | 174 ms | 0 |
| Wed 14 | 0 | 0.0 | 158 ms | 0 |
| Wed 16 | 0 | 0.0 | 146 ms | 0 |
| Wed 18 | 0 | 0.0 | 154 ms | 0 |
| Wed 21 | 0 | 0.0 | 155 ms | 0 |
| Wed 23 | 0 | 0.0 | 151 ms | 0 |
| Thu 01 | 0 | 0.0 | 174 ms | 0 |
| Thu 03 | 0 | 0.0 | 174 ms | 0 |
| Thu 05 | 0 | 0.0 | 149 ms | 0 |
| Thu 07 | 0 | 0.0 | 87 ms | 0 |
| Thu 09 | 0 | 0.0 | 139 ms | 0 |
| Thu 11 | 0 | 0.0 | 121 ms | 0 |
| Thu 13 | 0 | 0.0 | 177 ms | 0 |
| Thu 15 | 0 | 0.0 | 244 ms | 0 |
| Thu 17 | 0 | 0.0 | 216 ms | 0 |
| Thu 19 | 0 | 0.0 | 221 ms | 0 |
| Thu 22 | 0 | 0.0 | 90 ms | 0 |
| Fri 00 | 0 | 0.0 | 125 ms | 0 |
| Fri 02 | 0 | 0.0 | 182 ms | 0 |
| Fri 04 | 0 | 0.0 | 196 ms | 0 |
| Fri 07 | 0 | 0.0 | 197 ms | 0 |
| Fri 09 | 0 | 0.0 | 81 ms | 0 |
| Fri 11 | 0 | 0.0 | 155 ms | 0 |
| Fri 12 | 0 | 0.0 | 137 ms | 0 |
| Fri 14 | 0 | 0.0 | 214 ms | 0 |
| Fri 16 | 0 | 0.0 | 187 ms | 0 |
| Fri 18 | 0 | 0.0 | 203 ms | 0 |
| Fri 20 | 0 | 0.0 | 97 ms | 0 |
| Fri 21 | 0 | 0.0 | 242 ms | 0 |
| Fri 23 | 0 | 0.0 | 49 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 Fountain 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 Fountain yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fountain?
One report per service every 10 minutes from this network. No account.
Follow Fountain
Get an email when Fountain goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fountain alerts to Slack, Discord or a webhook — free.
About Fountain
We track Fountain (fountain.com) as part of the Cloud & developer group. Frontline Superintelligence. The #1 agent that runs your frontline operations
Fountain publishes an official status page at status.fountain.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 162 ms average, 49–246 ms range across 14 successful checks.
Questions
Is Fountain 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 Fountain last down?
We have not recorded a public Fountain incident since monitoring began 8 days ago.
What is Fountain's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Fountain respond?
162 ms on average over the last 24 hours (49–246 ms).
Does Fountain have an official status page?
Yes, at https://status.fountain.com.
Fountain 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 Fountain here at once, the problem is on Fountain'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 Fountain. 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.