User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
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 35 min ago. Last stored result reached it in 258 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 150 ms | 0 |
| Nov 7 | 0 | 0.0 | 133 ms | 0 |
| Nov 7 | 0 | 0.0 | 195 ms | 0 |
| Nov 7 | 0 | 0.0 | 169 ms | 0 |
| Nov 7 | 0 | 0.0 | 179 ms | 0 |
| Nov 8 | 0 | 0.0 | 183 ms | 0 |
| Nov 8 | 0 | 0.0 | 279 ms | 0 |
| Nov 8 | 0 | 0.0 | 154 ms | 0 |
| Nov 8 | 0 | 0.0 | 175 ms | 0 |
| Nov 9 | 0 | 0.0 | 158 ms | 0 |
| Nov 9 | 0 | 0.0 | 162 ms | 0 |
| Nov 9 | 0 | 0.0 | 255 ms | 0 |
| Nov 9 | 0 | 0.0 | 257 ms | 0 |
| Nov 10 | 0 | 0.0 | 204 ms | 0 |
| Nov 10 | 0 | 0.0 | 158 ms | 0 |
| Nov 10 | 0 | 0.0 | 177 ms | 0 |
| Nov 10 | 0 | 0.0 | 404 ms | 0 |
| Nov 11 | 0 | 0.0 | 272 ms | 0 |
| Nov 11 | 0 | 0.0 | 168 ms | 0 |
| Nov 11 | 0 | 0.0 | 193 ms | 0 |
| Nov 11 | 0 | 0.0 | 187 ms | 0 |
| Nov 12 | 0 | 0.0 | 205 ms | 0 |
| Nov 12 | 0 | 0.0 | 292 ms | 0 |
| Nov 12 | 0 | 0.0 | 201 ms | 0 |
| Nov 12 | 0 | 0.0 | 221 ms | 0 |
| Nov 13 | 0 | 0.0 | 201 ms | 0 |
| Nov 13 | 0 | 0.0 | 149 ms | 0 |
| Nov 13 | 0 | 0.0 | 195 ms | 0 |
| Nov 13 | 0 | 0.0 | 231 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 Fairing 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 Fairing goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fairing alerts to Slack, Discord or a webhook — free.
We track Fairing (fairing.co) as part of the Shopping group. Ask buyers how they found you, why they bought and what almost stopped them, right after checkout. Trusted by 3,500+ ecommerce brands.
Fairing publishes an official status page at status.fairing.co; when we can read it, its incident level is folded into the status shown here.
Common problems for shopping services: checkout and payment errors, carts not loading, and order tracking 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: 193 ms average, 111–284 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Fairing incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
193 ms on average over the last 24 hours (111–284 ms).
Yes, at https://status.fairing.co.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For shopping services, watch for checkout and payment errors, carts not loading, and order tracking problems. If many people report Fairing here at once, the problem is on Fairing'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 Fairing. 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.