User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 5 min ago. Last stored result reached it in 177 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 16 | 0 | 0.0 | 182 ms | 0 |
| Tue 18 | 0 | 0.0 | 202 ms | 0 |
| Tue 21 | 0 | 0.0 | 143 ms | 0 |
| Tue 23 | 0 | 0.0 | 238 ms | 0 |
| Wed 01 | 0 | 0.0 | 269 ms | 0 |
| Wed 03 | 0 | 0.0 | 162 ms | 0 |
| Wed 06 | 0 | 0.0 | 176 ms | 0 |
| Wed 08 | 0 | 0.0 | 171 ms | 0 |
| Wed 10 | 0 | 0.0 | 206 ms | 0 |
| Wed 12 | 0 | 0.0 | 186 ms | 0 |
| Wed 14 | 0 | 0.0 | 197 ms | 0 |
| Wed 16 | 0 | 0.0 | 147 ms | 0 |
| Wed 19 | 0 | 0.0 | 107 ms | 0 |
| Wed 21 | 0 | 0.0 | 359 ms | 0 |
| Wed 23 | 0 | 0.0 | 160 ms | 0 |
| Thu 01 | 0 | 0.0 | 156 ms | 0 |
| Thu 03 | 0 | 0.0 | 100 ms | 0 |
| Thu 05 | 0 | 0.0 | 184 ms | 0 |
| Thu 07 | 0 | 0.0 | 182 ms | 0 |
| Thu 09 | 0 | 0.0 | 142 ms | 0 |
| Thu 11 | 0 | 0.0 | 178 ms | 0 |
| Thu 14 | 0 | 0.0 | 193 ms | 0 |
| Thu 16 | 0 | 0.0 | 195 ms | 0 |
| Thu 17 | 0 | 0.0 | 217 ms | 0 |
| Thu 19 | 0 | 0.0 | 394 ms | 0 |
| Thu 21 | 0 | 0.0 | 191 ms | 0 |
| Thu 23 | 0 | 0.0 | 515 ms | 0 |
| Fri 01 | 0 | 0.0 | 179 ms | 0 |
| Fri 03 | 0 | 0.0 | 354 ms | 0 |
| Fri 05 | 0 | 0.0 | 128 ms | 0 |
| Fri 07 | 0 | 0.0 | 239 ms | 0 |
| Fri 09 | 0 | 0.0 | 159 ms | 0 |
| Fri 10 | 0 | 0.0 | 96 ms | 0 |
| Fri 11 | 0 | 0.0 | 175 ms | 0 |
| Fri 12 | 0 | 0.0 | 184 ms | 0 |
| Fri 14 | 0 | 0.0 | 122 ms | 0 |
| Fri 16 | 0 | 0.0 | 167 ms | 0 |
| Fri 18 | 0 | 0.0 | 159 ms | 0 |
| Fri 19 | 0 | 0.0 | 146 ms | 0 |
| Fri 21 | 0 | 0.0 | 196 ms | 0 |
| Fri 22 | 0 | 0.0 | 170 ms | 0 |
| Sat 00 | 0 | 0.0 | 665 ms | 0 |
| Sat 02 | 0 | 0.0 | 199 ms | 0 |
| Sat 03 | 0 | 0.0 | 134 ms | 0 |
| Sat 04 | 0 | 0.0 | 151 ms | 0 |
| Sat 05 | 0 | 0.0 | 157 ms | 0 |
| Sat 07 | 0 | 0.0 | 173 ms | 0 |
| Sat 09 | 0 | 0.0 | 177 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Notifiarr 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 Notifiarr goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Notifiarr alerts to Slack, Discord or a webhook — free.
We track Notifiarr (notifiarr.com) as part of the Social group. Automated discord notifications and more
Notifiarr publishes an official status page at status.notifiarr.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 190 ms average, 96–665 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Notifiarr incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
190 ms on average over the last 24 hours (96–665 ms).
Yes, at https://status.notifiarr.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Notifiarr here at once, the problem is on Notifiarr'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 Notifiarr. 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.