User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 1 hr ago. Last stored result reached it in 138 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 295 ms | 0 |
| Mon 16 | 0 | 0.0 | 279 ms | 0 |
| Mon 18 | 0 | 0.0 | 272 ms | 0 |
| Mon 20 | 0 | 0.0 | 168 ms | 0 |
| Mon 23 | 0 | 0.0 | 291 ms | 0 |
| Tue 01 | 0 | 0.0 | 203 ms | 0 |
| Tue 03 | 0 | 0.0 | 294 ms | 0 |
| Tue 05 | 0 | 0.0 | 298 ms | 0 |
| Tue 07 | 0 | 0.0 | 304 ms | 0 |
| Tue 09 | 0 | 0.0 | 308 ms | 0 |
| Tue 11 | 0 | 0.0 | 315 ms | 0 |
| Tue 13 | 0 | 0.0 | — | 0 |
| Tue 14 | 0 | 0.0 | 121 ms | 0 |
| Tue 16 | 0 | 0.0 | 282 ms | 0 |
| Tue 18 | 0 | 0.0 | 368 ms | 0 |
| Tue 20 | 0 | 0.0 | 215 ms | 0 |
| Tue 23 | 0 | 0.0 | 305 ms | 0 |
| Wed 01 | 0 | 0.0 | 233 ms | 0 |
| Wed 03 | 0 | 0.0 | 294 ms | 0 |
| Wed 05 | 0 | 0.0 | 351 ms | 0 |
| Wed 07 | 0 | 0.0 | 289 ms | 0 |
| Wed 10 | 0 | 0.0 | 352 ms | 0 |
| Wed 12 | 0 | 0.0 | 347 ms | 0 |
| Wed 14 | 0 | 0.0 | 257 ms | 0 |
| Wed 16 | 0 | 0.0 | 174 ms | 0 |
| Wed 18 | 0 | 0.0 | 252 ms | 0 |
| Wed 21 | 0 | 0.0 | 211 ms | 0 |
| Wed 23 | 0 | 0.0 | 284 ms | 0 |
| Thu 01 | 0 | 0.0 | 233 ms | 0 |
| Thu 03 | 0 | 0.0 | 308 ms | 0 |
| Thu 05 | 0 | 0.0 | 338 ms | 0 |
| Thu 07 | 0 | 0.0 | 290 ms | 0 |
| Thu 09 | 0 | 0.0 | 257 ms | 0 |
| Thu 11 | 0 | 0.0 | 262 ms | 0 |
| Thu 13 | 0 | 0.0 | 200 ms | 0 |
| Thu 15 | 0 | 0.0 | 219 ms | 0 |
| Thu 17 | 0 | 0.0 | 339 ms | 0 |
| Thu 19 | 0 | 0.0 | 350 ms | 0 |
| Thu 21 | 0 | 0.0 | 289 ms | 0 |
| Fri 00 | 0 | 0.0 | 158 ms | 0 |
| Fri 02 | 0 | 0.0 | 332 ms | 0 |
| Fri 04 | 0 | 0.0 | 297 ms | 0 |
| Fri 06 | 0 | 0.0 | 352 ms | 0 |
| Fri 08 | 0 | 0.0 | 289 ms | 0 |
| Fri 10 | 0 | 0.0 | 305 ms | 0 |
| Fri 12 | 0 | 0.0 | 258 ms | 0 |
| Fri 14 | 0 | 0.0 | 345 ms | 0 |
| Fri 16 | 0 | 0.0 | 138 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 FeedBlitz 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 FeedBlitz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FeedBlitz alerts to Slack, Discord or a webhook — free.
We track FeedBlitz (feedblitz.com) as part of the Productivity group. Email marketing is getting harder to do well. This is all we do. Realize your success, get your word out and relax just a little more. FeedBlitz can help.
FeedBlitz publishes an official status page at status.feedblitz.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 271 ms average, 84–352 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 FeedBlitz incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
271 ms on average over the last 24 hours (84–352 ms).
Yes, at https://status.feedblitz.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report FeedBlitz here at once, the problem is on FeedBlitz'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 FeedBlitz. 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.