User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
marfeel.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 24 min ago. Last stored result reached it in 170 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 165 ms | 0 |
| Mon 23 | 0 | 0.0 | 110 ms | 0 |
| Tue 01 | 0 | 0.0 | 131 ms | 0 |
| Tue 03 | 0 | 0.0 | 129 ms | 0 |
| Tue 05 | 0 | 0.0 | 105 ms | 0 |
| Tue 07 | 0 | 0.0 | 362 ms | 0 |
| Tue 10 | 0 | 0.0 | 111 ms | 0 |
| Tue 12 | 0 | 0.0 | 294 ms | 0 |
| Tue 14 | 0 | 0.0 | 176 ms | 0 |
| Tue 16 | 0 | 0.0 | 324 ms | 0 |
| Tue 18 | 0 | 0.0 | 113 ms | 0 |
| Tue 21 | 0 | 0.0 | 90 ms | 0 |
| Tue 23 | 0 | 0.0 | 296 ms | 0 |
| Wed 01 | 0 | 0.0 | 127 ms | 0 |
| Wed 03 | 0 | 0.0 | 143 ms | 0 |
| Wed 06 | 0 | 0.0 | 137 ms | 0 |
| Wed 08 | 0 | 0.0 | 39 ms | 0 |
| Wed 10 | 0 | 0.0 | 748 ms | 0 |
| Wed 12 | 0 | 0.0 | 1332 ms | 0 |
| Wed 14 | 0 | 0.0 | 418 ms | 0 |
| Wed 16 | 0 | 0.0 | 189 ms | 0 |
| Wed 19 | 0 | 0.0 | 143 ms | 0 |
| Wed 21 | 0 | 0.0 | 174 ms | 0 |
| Wed 23 | 0 | 0.0 | 94 ms | 0 |
| Thu 01 | 0 | 0.0 | 150 ms | 0 |
| Thu 03 | 0 | 0.0 | 795 ms | 0 |
| Thu 05 | 0 | 0.0 | 123 ms | 0 |
| Thu 07 | 0 | 0.0 | 279 ms | 0 |
| Thu 09 | 0 | 0.0 | 170 ms | 0 |
| Thu 12 | 0 | 0.0 | 155 ms | 0 |
| Thu 14 | 0 | 0.0 | 98 ms | 0 |
| Thu 16 | 0 | 0.0 | 128 ms | 0 |
| Thu 18 | 0 | 0.0 | 179 ms | 0 |
| Thu 19 | 0 | 0.0 | 254 ms | 0 |
| Thu 21 | 0 | 0.0 | 85 ms | 0 |
| Thu 23 | 0 | 0.0 | 317 ms | 0 |
| Fri 01 | 0 | 0.0 | 108 ms | 0 |
| Fri 03 | 0 | 0.0 | 496 ms | 0 |
| Fri 05 | 0 | 0.0 | 132 ms | 0 |
| Fri 07 | 0 | 0.0 | 251 ms | 0 |
| Fri 09 | 0 | 0.0 | 467 ms | 0 |
| Fri 10 | 0 | 0.0 | 441 ms | 0 |
| Fri 12 | 0 | 0.0 | 149 ms | 0 |
| Fri 14 | 0 | 0.0 | 202 ms | 0 |
| Fri 16 | 0 | 0.0 | 358 ms | 0 |
| Fri 18 | 0 | 0.0 | 173 ms | 0 |
| Fri 20 | 0 | 0.0 | 308 ms | 0 |
| Fri 22 | 0 | 0.0 | 170 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 Marfeel 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 Marfeel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Marfeel alerts to Slack, Discord or a webhook — free.
We track Marfeel (marfeel.com) as part of the Cloud & developer group. A suite of solutions designed for every publisher's needs
Marfeel publishes an official status page at status.marfeel.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: 277 ms average, 108–496 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 Marfeel incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
277 ms on average over the last 24 hours (108–496 ms).
Yes, at https://status.marfeel.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 Marfeel here at once, the problem is on Marfeel'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 Marfeel. 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.