User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
primfeed.com · Cloud & developer
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 43 min ago. Last stored result reached it in 388 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 320 ms | 0 |
| Mon 15 | 0 | 0.0 | 267 ms | 0 |
| Mon 17 | 0 | 0.0 | 229 ms | 0 |
| Mon 19 | 0 | 0.0 | 232 ms | 0 |
| Mon 21 | 0 | 0.0 | 171 ms | 0 |
| Mon 23 | 0 | 0.0 | 241 ms | 0 |
| Tue 01 | 0 | 0.0 | 353 ms | 0 |
| Tue 03 | 0 | 0.0 | 215 ms | 0 |
| Tue 06 | 0 | 0.0 | 208 ms | 0 |
| Tue 08 | 0 | 0.0 | 742 ms | 0 |
| Tue 10 | 0 | 0.0 | 176 ms | 0 |
| Tue 12 | 0 | 0.0 | 190 ms | 0 |
| Tue 14 | 0 | 0.0 | 251 ms | 0 |
| Tue 16 | 0 | 0.0 | 205 ms | 0 |
| Tue 19 | 0 | 0.0 | 182 ms | 0 |
| Tue 21 | 0 | 0.0 | 737 ms | 0 |
| Tue 23 | 0 | 0.0 | 177 ms | 0 |
| Wed 01 | 0 | 0.0 | 371 ms | 0 |
| Wed 04 | 0 | 0.0 | 243 ms | 0 |
| Wed 06 | 0 | 0.0 | 209 ms | 0 |
| Wed 08 | 0 | 0.0 | 374 ms | 0 |
| Wed 10 | 0 | 0.0 | 183 ms | 0 |
| Wed 13 | 0 | 0.0 | 338 ms | 0 |
| Wed 15 | 0 | 0.0 | 823 ms | 0 |
| Wed 17 | 0 | 0.0 | 399 ms | 0 |
| Wed 19 | 0 | 0.0 | 205 ms | 0 |
| Wed 21 | 0 | 0.0 | 283 ms | 0 |
| Wed 23 | 0 | 0.0 | 264 ms | 0 |
| Thu 02 | 0 | 0.0 | 196 ms | 0 |
| Thu 04 | 0 | 0.0 | 866 ms | 0 |
| Thu 06 | 0 | 0.0 | 922 ms | 0 |
| Thu 08 | 0 | 0.0 | 878 ms | 0 |
| Thu 10 | 0 | 0.0 | 665 ms | 0 |
| Thu 12 | 0 | 0.0 | 824 ms | 0 |
| Thu 14 | 0 | 0.0 | 255 ms | 0 |
| Thu 16 | 0 | 0.0 | 233 ms | 0 |
| Thu 18 | 0 | 0.0 | 150 ms | 0 |
| Thu 20 | 0 | 0.0 | 329 ms | 0 |
| Thu 22 | 0 | 0.0 | 174 ms | 0 |
| Fri 00 | 0 | 0.0 | 207 ms | 0 |
| Fri 02 | 0 | 0.0 | 202 ms | 0 |
| Fri 04 | 0 | 0.0 | 208 ms | 0 |
| Fri 06 | 0 | 0.0 | 195 ms | 0 |
| Fri 09 | 0 | 0.0 | 482 ms | 0 |
| Fri 11 | 0 | 0.0 | 600 ms | 0 |
| Fri 13 | 0 | 0.0 | 203 ms | 0 |
| Fri 15 | 0 | 0.0 | 749 ms | 0 |
| Fri 17 | 0 | 0.0 | 331 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 Primfeed 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 Primfeed goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Primfeed alerts to Slack, Discord or a webhook — free.
We track Primfeed (primfeed.com) as part of the Cloud & developer group. Share high-quality photos and videos, connect with residents, follow brands, and discover what's happening in this virtual world.
Primfeed publishes an official status page at status.primfeed.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 327 ms average, 163–801 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Primfeed incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
327 ms on average over the last 24 hours (163–801 ms).
Yes, at https://status.primfeed.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Primfeed here at once, the problem is on Primfeed'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 Primfeed. 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.