User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 48 min ago. Last stored result reached it in 255 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 307 ms | 0 |
| Tue 01 | 0 | 0.0 | 276 ms | 0 |
| Tue 03 | 0 | 0.0 | 318 ms | 0 |
| Tue 06 | 0 | 0.0 | 273 ms | 0 |
| Tue 08 | 0 | 0.0 | 316 ms | 0 |
| Tue 10 | 0 | 0.0 | 283 ms | 0 |
| Tue 12 | 0 | 0.0 | 217 ms | 0 |
| Tue 14 | 0 | 0.0 | 394 ms | 0 |
| Tue 16 | 0 | 0.0 | 236 ms | 0 |
| Tue 19 | 0 | 0.0 | 312 ms | 0 |
| Tue 21 | 0 | 0.0 | 159 ms | 0 |
| Tue 23 | 0 | 0.0 | 169 ms | 0 |
| Wed 01 | 0 | 0.0 | 315 ms | 0 |
| Wed 04 | 0 | 0.0 | 294 ms | 0 |
| Wed 06 | 0 | 0.0 | 308 ms | 0 |
| Wed 08 | 0 | 0.0 | 278 ms | 0 |
| Wed 10 | 0 | 0.0 | 319 ms | 0 |
| Wed 13 | 0 | 0.0 | 302 ms | 0 |
| Wed 15 | 0 | 0.0 | 278 ms | 0 |
| Wed 17 | 0 | 0.0 | 167 ms | 0 |
| Wed 19 | 0 | 0.0 | 169 ms | 0 |
| Wed 21 | 0 | 0.0 | 335 ms | 0 |
| Wed 23 | 0 | 0.0 | 144 ms | 0 |
| Thu 02 | 0 | 0.0 | 289 ms | 0 |
| Thu 04 | 0 | 0.0 | 259 ms | 0 |
| Thu 06 | 0 | 0.0 | 156 ms | 0 |
| Thu 08 | 0 | 0.0 | 258 ms | 0 |
| Thu 10 | 0 | 0.0 | 278 ms | 0 |
| Thu 12 | 0 | 0.0 | 353 ms | 0 |
| Thu 14 | 0 | 0.0 | 256 ms | 0 |
| Thu 16 | 0 | 0.0 | 263 ms | 0 |
| Thu 18 | 0 | 0.0 | 313 ms | 0 |
| Thu 20 | 0 | 0.0 | 169 ms | 0 |
| Thu 22 | 0 | 0.0 | 148 ms | 0 |
| Fri 00 | 0 | 0.0 | 279 ms | 0 |
| Fri 02 | 0 | 0.0 | 243 ms | 0 |
| Fri 04 | 0 | 0.0 | 302 ms | 0 |
| Fri 07 | 0 | 0.0 | 294 ms | 0 |
| Fri 08 | 0 | 0.0 | 298 ms | 0 |
| Fri 11 | 0 | 0.0 | 280 ms | 0 |
| Fri 13 | 0 | 0.0 | 278 ms | 0 |
| Fri 15 | 0 | 0.0 | 290 ms | 0 |
| Fri 17 | 0 | 0.0 | 334 ms | 0 |
| Fri 19 | 0 | 0.0 | 266 ms | 0 |
| Fri 21 | 0 | 0.0 | 259 ms | 0 |
| Fri 23 | 0 | 0.0 | 258 ms | 0 |
| Sat 00 | 0 | 0.0 | 298 ms | 0 |
| Sat 02 | 0 | 0.0 | 255 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 Referrizer 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 Referrizer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Referrizer alerts to Slack, Discord or a webhook — free.
We track Referrizer (business.referrizer.com) as part of the AI group. Referral campaigns, review requests, 2-way texting, and a 24/7 AI assistant in one platform: marketing automation for small business, from 1 location to 1,000s.
Referrizer publishes an official status page at status.referrizer.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 285 ms average, 255–334 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Referrizer incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
285 ms on average over the last 24 hours (255–334 ms).
Yes, at https://status.referrizer.com.
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 Referrizer here at once, the problem is on Referrizer'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 Referrizer. 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.