User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 35 min ago. Last stored result reached it in 77 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 | 1743 ms | 0 |
| Nov 7 | 0 | 0.0 | 1636 ms | 0 |
| Nov 7 | 0 | 0.0 | 1453 ms | 0 |
| Nov 7 | 0 | 0.0 | 1501 ms | 0 |
| Nov 7 | 0 | 0.0 | 1744 ms | 0 |
| Nov 8 | 0 | 0.0 | 1865 ms | 0 |
| Nov 8 | 0 | 0.0 | 1580 ms | 0 |
| Nov 8 | 0 | 0.0 | 1585 ms | 0 |
| Nov 8 | 0 | 0.0 | 1595 ms | 0 |
| Nov 9 | 0 | 0.0 | 1621 ms | 0 |
| Nov 9 | 0 | 0.0 | 1618 ms | 0 |
| Nov 9 | 0 | 0.0 | 1686 ms | 0 |
| Nov 9 | 0 | 0.0 | 1692 ms | 0 |
| Nov 10 | 0 | 0.0 | 1592 ms | 0 |
| Nov 10 | 0 | 0.0 | 1507 ms | 0 |
| Nov 10 | 0 | 0.0 | 1752 ms | 0 |
| Nov 10 | 0 | 0.0 | 1631 ms | 0 |
| Nov 11 | 0 | 0.0 | 1682 ms | 0 |
| Nov 11 | 0 | 0.0 | 1679 ms | 0 |
| Nov 11 | 0 | 0.0 | 1830 ms | 0 |
| Nov 11 | 0 | 0.0 | 1664 ms | 0 |
| Nov 12 | 0 | 0.0 | 1565 ms | 0 |
| Nov 12 | 0 | 0.0 | 1638 ms | 0 |
| Nov 12 | 0 | 0.0 | 97 ms | 0 |
| Nov 12 | 0 | 0.0 | 88 ms | 0 |
| Nov 13 | 0 | 0.0 | 122 ms | 0 |
| Nov 13 | 0 | 0.0 | 105 ms | 0 |
| Nov 13 | 0 | 0.0 | 151 ms | 0 |
| Nov 13 | 0 | 0.0 | 101 ms | 0 |
| Nov 14 | 0 | 0.0 | 89 ms | 0 |
| Nov 14 | 0 | 0.0 | 140 ms | 0 |
| Nov 14 | 0 | 0.0 | 147 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 Taggrs.io 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 Taggrs.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Taggrs.io alerts to Slack, Discord or a webhook — free.
Taggrs.io is listed in our Cloud & developer category and checked at taggrs.io. Recover the data ad blockers, ITP, and cookie restrictions block. TAGGRS is the hosted server-side tracking platform for complete data across every channel. Start free.
Taggrs.io publishes an official status page at status.taggrs.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 127 ms average, 77–217 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 Taggrs.io incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
127 ms on average over the last 24 hours (77–217 ms).
Yes, at https://status.taggrs.io.
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 Taggrs.io here at once, the problem is on Taggrs.io'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 Taggrs.io. 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.