User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Frigade 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 → frigade.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 22 min ago. Last stored result reached it in 204 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 15 | 0 | 0.0 | 141 ms | 0 |
| Mon 17 | 0 | 0.0 | 131 ms | 0 |
| Mon 20 | 0 | 0.0 | 176 ms | 0 |
| Mon 22 | 0 | 0.0 | 152 ms | 0 |
| Tue 00 | 0 | 0.0 | 159 ms | 0 |
| Tue 02 | 0 | 0.0 | 105 ms | 0 |
| Tue 04 | 0 | 0.0 | 233 ms | 0 |
| Tue 06 | 0 | 0.0 | 117 ms | 0 |
| Tue 08 | 0 | 0.0 | 168 ms | 0 |
| Tue 10 | 0 | 0.0 | 223 ms | 0 |
| Tue 12 | 0 | 0.0 | 72 ms | 0 |
| Tue 15 | 0 | 0.0 | 157 ms | 0 |
| Tue 17 | 0 | 0.0 | 354 ms | 0 |
| Tue 19 | 0 | 0.0 | 74 ms | 0 |
| Tue 21 | 0 | 0.0 | 70 ms | 0 |
| Wed 00 | 0 | 0.0 | 209 ms | 0 |
| Wed 02 | 0 | 0.0 | 53 ms | 0 |
| Wed 04 | 0 | 0.0 | 128 ms | 0 |
| Wed 06 | 0 | 0.0 | 318 ms | 0 |
| Wed 09 | 0 | 0.0 | 174 ms | 0 |
| Wed 11 | 0 | 0.0 | 162 ms | 0 |
| Wed 13 | 0 | 0.0 | 141 ms | 0 |
| Wed 15 | 0 | 0.0 | 196 ms | 0 |
| Wed 17 | 0 | 0.0 | 315 ms | 0 |
| Wed 19 | 0 | 0.0 | 183 ms | 0 |
| Wed 22 | 0 | 0.0 | 105 ms | 0 |
| Thu 00 | 0 | 0.0 | 141 ms | 0 |
| Thu 01 | 0 | 0.0 | 179 ms | 0 |
| Thu 03 | 0 | 0.0 | 215 ms | 0 |
| Thu 05 | 0 | 0.0 | 363 ms | 0 |
| Thu 07 | 0 | 0.0 | 150 ms | 0 |
| Thu 09 | 0 | 0.0 | 166 ms | 0 |
| Thu 11 | 0 | 0.0 | 162 ms | 0 |
| Thu 13 | 0 | 0.0 | 162 ms | 0 |
| Thu 15 | 0 | 0.0 | 217 ms | 0 |
| Thu 17 | 0 | 0.0 | 607 ms | 0 |
| Thu 19 | 0 | 0.0 | 204 ms | 0 |
| Thu 21 | 0 | 0.0 | 163 ms | 0 |
| Thu 23 | 0 | 0.0 | 158 ms | 0 |
| Fri 01 | 0 | 0.0 | 138 ms | 0 |
| Fri 03 | 0 | 0.0 | 76 ms | 0 |
| Fri 06 | 0 | 0.0 | 233 ms | 0 |
| Fri 08 | 0 | 0.0 | 97 ms | 0 |
| Fri 10 | 0 | 0.0 | 125 ms | 0 |
| Fri 11 | 0 | 0.0 | 185 ms | 0 |
| Fri 13 | 0 | 0.0 | 115 ms | 0 |
| Fri 15 | 0 | 0.0 | 55 ms | 0 |
| Fri 17 | 0 | 0.0 | 204 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 Frigade 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 Frigade yet. Outages of 10 minutes or more get their own page here.
Having trouble with Frigade?
One report per service every 10 minutes from this network. No account.
Follow Frigade
Get an email when Frigade goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Frigade alerts to Slack, Discord or a webhook — free.
About Frigade
We track Frigade (frigade.com) as part of the AI group. Frigade is an AI-native digital adoption platform. Frigade Assistant lives inside your product, learns it by using it, answers user questions, and takes the action with them in real time. No flows to design, no docs to maintain.
Frigade publishes an official status page at status.frigade.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 140 ms average, 55–233 ms range across 14 successful checks.
Questions
Is Frigade down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Frigade last down?
We have not recorded a public Frigade incident since monitoring began 8 days ago.
What is Frigade's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Frigade respond?
140 ms on average over the last 24 hours (55–233 ms).
Does Frigade have an official status page?
Yes, at https://status.frigade.com.
Frigade 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Frigade here at once, the problem is on Frigade'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 Frigade. 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.