User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Rapidflare 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 → rapidflare.ai—
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 2 hr ago. Last stored result reached it in 259 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 | 214 ms | 0 |
| Mon 23 | 0 | 0.0 | 219 ms | 0 |
| Tue 01 | 0 | 0.0 | 188 ms | 0 |
| Tue 03 | 0 | 0.0 | 130 ms | 0 |
| Tue 05 | 0 | 0.0 | 98 ms | 0 |
| Tue 07 | 0 | 0.0 | 93 ms | 0 |
| Tue 09 | 0 | 0.0 | 248 ms | 0 |
| Tue 11 | 0 | 0.0 | 108 ms | 0 |
| Tue 14 | 0 | 0.0 | 155 ms | 0 |
| Tue 16 | 0 | 0.0 | 112 ms | 0 |
| Tue 18 | 0 | 0.0 | 915 ms | 0 |
| Tue 20 | 0 | 0.0 | 336 ms | 0 |
| Tue 23 | 0 | 0.0 | 260 ms | 0 |
| Wed 01 | 0 | 0.0 | 198 ms | 0 |
| Wed 03 | 0 | 0.0 | 248 ms | 0 |
| Wed 05 | 0 | 0.0 | 126 ms | 0 |
| Wed 08 | 0 | 0.0 | 82 ms | 0 |
| Wed 10 | 0 | 0.0 | 129 ms | 0 |
| Wed 12 | 0 | 0.0 | 157 ms | 0 |
| Wed 14 | 0 | 0.0 | 114 ms | 0 |
| Wed 16 | 0 | 0.0 | 175 ms | 0 |
| Wed 18 | 0 | 0.0 | 100 ms | 0 |
| Wed 21 | 0 | 0.0 | 163 ms | 0 |
| Wed 23 | 0 | 0.0 | 135 ms | 0 |
| Thu 01 | 0 | 0.0 | 133 ms | 0 |
| Thu 03 | 0 | 0.0 | 305 ms | 0 |
| Thu 05 | 0 | 0.0 | 116 ms | 0 |
| Thu 07 | 0 | 0.0 | 136 ms | 0 |
| Thu 09 | 0 | 0.0 | 297 ms | 0 |
| Thu 11 | 0 | 0.0 | 156 ms | 0 |
| Thu 13 | 0 | 0.0 | 120 ms | 0 |
| Thu 16 | 0 | 0.0 | 257 ms | 0 |
| Thu 18 | 0 | 0.0 | 365 ms | 0 |
| Thu 20 | 0 | 0.0 | 330 ms | 0 |
| Thu 22 | 0 | 0.0 | 135 ms | 0 |
| Thu 23 | 0 | 0.0 | 104 ms | 0 |
| Fri 01 | 0 | 0.0 | 156 ms | 0 |
| Fri 03 | 0 | 0.0 | 136 ms | 0 |
| Fri 05 | 0 | 0.0 | 137 ms | 0 |
| Fri 07 | 0 | 0.0 | 455 ms | 0 |
| Fri 09 | 0 | 0.0 | 92 ms | 0 |
| Fri 10 | 0 | 0.0 | 120 ms | 0 |
| Fri 12 | 0 | 0.0 | 177 ms | 0 |
| Fri 14 | 0 | 0.0 | 363 ms | 0 |
| Fri 16 | 0 | 0.0 | 159 ms | 0 |
| Fri 17 | 0 | 0.0 | 131 ms | 0 |
| Fri 19 | 0 | 0.0 | 116 ms | 0 |
| Fri 21 | 0 | 0.0 | 259 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Rapidflare 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 Rapidflare yet. Outages of 10 minutes or more get their own page here.
Having trouble with Rapidflare?
One report per service every 10 minutes from this network. No account.
Follow Rapidflare
Get an email when Rapidflare goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rapidflare alerts to Slack, Discord or a webhook — free.
About Rapidflare
We track Rapidflare (rapidflare.ai) as part of the AI group. AI agents that answer product selection, cross-reference and support questions from your datasheets and docs. Cited on every line. See it on your parts.
Rapidflare publishes an official status page at status.rapidflare.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 178 ms average, 67–455 ms range across 14 successful checks.
Questions
Is Rapidflare down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Rapidflare last down?
We have not recorded a public Rapidflare incident since monitoring began 6 days ago.
What is Rapidflare's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Rapidflare respond?
178 ms on average over the last 24 hours (67–455 ms).
Does Rapidflare have an official status page?
Yes, at https://status.rapidflare.ai.
Rapidflare 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 Rapidflare here at once, the problem is on Rapidflare'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 Rapidflare. 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.