User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
embeddable.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 16 min ago. Last stored result reached it in 208 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 10 | 0 | 0.0 | 414 ms | 0 |
| Mon 12 | 0 | 0.0 | 85 ms | 0 |
| Mon 14 | 0 | 0.0 | 212 ms | 0 |
| Mon 16 | 0 | 0.0 | 174 ms | 0 |
| Mon 18 | 0 | 0.0 | 155 ms | 0 |
| Mon 20 | 0 | 0.0 | 418 ms | 0 |
| Mon 23 | 0 | 0.0 | 84 ms | 0 |
| Tue 01 | 0 | 0.0 | 215 ms | 0 |
| Tue 03 | 0 | 0.0 | 327 ms | 0 |
| Tue 05 | 0 | 0.0 | 122 ms | 0 |
| Tue 07 | 0 | 0.0 | 80 ms | 0 |
| Tue 09 | 0 | 0.0 | 188 ms | 0 |
| Tue 11 | 0 | 0.0 | 184 ms | 0 |
| Tue 13 | 0 | 0.0 | 217 ms | 0 |
| Tue 16 | 0 | 0.0 | 114 ms | 0 |
| Tue 18 | 0 | 0.0 | 113 ms | 0 |
| Tue 20 | 0 | 0.0 | 176 ms | 0 |
| Tue 22 | 0 | 0.0 | 211 ms | 0 |
| Wed 01 | 0 | 0.0 | 89 ms | 0 |
| Wed 03 | 0 | 0.0 | 141 ms | 0 |
| Wed 05 | 0 | 0.0 | 134 ms | 0 |
| Wed 07 | 0 | 0.0 | 194 ms | 0 |
| Wed 10 | 0 | 0.0 | 170 ms | 0 |
| Wed 12 | 0 | 0.0 | 145 ms | 0 |
| Wed 14 | 0 | 0.0 | 188 ms | 0 |
| Wed 16 | 0 | 0.0 | 199 ms | 0 |
| Wed 18 | 0 | 0.0 | 140 ms | 0 |
| Wed 20 | 0 | 0.0 | 99 ms | 0 |
| Wed 23 | 0 | 0.0 | 160 ms | 0 |
| Thu 01 | 0 | 0.0 | 198 ms | 0 |
| Thu 03 | 0 | 0.0 | 160 ms | 0 |
| Thu 05 | 0 | 0.0 | 280 ms | 0 |
| Thu 07 | 0 | 0.0 | 198 ms | 0 |
| Thu 09 | 0 | 0.0 | 137 ms | 0 |
| Thu 11 | 0 | 0.0 | 74 ms | 0 |
| Thu 13 | 0 | 0.0 | 183 ms | 0 |
| Thu 15 | 0 | 0.0 | 147 ms | 0 |
| Thu 17 | 0 | 0.0 | 183 ms | 0 |
| Thu 19 | 0 | 0.0 | 178 ms | 0 |
| Thu 21 | 0 | 0.0 | 133 ms | 0 |
| Thu 23 | 0 | 0.0 | 114 ms | 0 |
| Fri 01 | 0 | 0.0 | 166 ms | 0 |
| Fri 04 | 0 | 0.0 | 157 ms | 0 |
| Fri 06 | 0 | 0.0 | 83 ms | 0 |
| Fri 08 | 0 | 0.0 | 128 ms | 0 |
| Fri 10 | 0 | 0.0 | 78 ms | 0 |
| Fri 11 | 0 | 0.0 | 131 ms | 0 |
| Fri 13 | 0 | 0.0 | 208 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Embeddable 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 Embeddable goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Embeddable alerts to Slack, Discord or a webhook — free.
Embeddable is listed in our Cloud & developer category and checked at embeddable.com. Embedded analytics, done right. Embeddable is a developer toolkit for crafting remarkable customer-facing analytics experiences into your app.
Embeddable publishes an official status page at status.embeddable.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 138 ms average, 64–208 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 Embeddable incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
138 ms on average over the last 24 hours (64–208 ms).
Yes, at https://status.embeddable.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 Embeddable here at once, the problem is on Embeddable'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 Embeddable. 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.