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 52 min ago. Last stored result reached it in 143 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 161 ms | 0 |
| Mon 15 | 0 | 0.0 | 521 ms | 0 |
| Mon 17 | 0 | 0.0 | 341 ms | 0 |
| Mon 19 | 0 | 0.0 | 190 ms | 0 |
| Mon 21 | 0 | 0.0 | 298 ms | 0 |
| Mon 23 | 0 | 0.0 | 475 ms | 0 |
| Tue 01 | 0 | 0.0 | 454 ms | 0 |
| Tue 03 | 0 | 0.0 | 438 ms | 0 |
| Tue 05 | 0 | 0.0 | 361 ms | 0 |
| Tue 07 | 0 | 0.0 | 366 ms | 0 |
| Tue 09 | 0 | 0.0 | 290 ms | 0 |
| Tue 12 | 0 | 0.0 | 437 ms | 0 |
| Tue 14 | 0 | 0.0 | 122 ms | 0 |
| Tue 16 | 0 | 0.0 | 436 ms | 0 |
| Tue 18 | 0 | 0.0 | 547 ms | 0 |
| Tue 21 | 0 | 0.0 | 320 ms | 0 |
| Tue 23 | 0 | 0.0 | 118 ms | 0 |
| Wed 01 | 0 | 0.0 | 516 ms | 0 |
| Wed 03 | 0 | 0.0 | 338 ms | 0 |
| Wed 06 | 0 | 0.0 | 737 ms | 0 |
| Wed 08 | 0 | 0.0 | 655 ms | 0 |
| Wed 10 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 384 ms | 0 |
| Wed 14 | 0 | 0.0 | 647 ms | 0 |
| Wed 16 | 0 | 0.0 | 668 ms | 0 |
| Wed 19 | 0 | 0.0 | 450 ms | 0 |
| Wed 21 | 0 | 0.0 | 95 ms | 0 |
| Wed 23 | 0 | 0.0 | 606 ms | 0 |
| Thu 01 | 0 | 0.0 | 469 ms | 0 |
| Thu 03 | 0 | 0.0 | 142 ms | 0 |
| Thu 05 | 0 | 0.0 | 302 ms | 0 |
| Thu 07 | 0 | 0.0 | 178 ms | 0 |
| Thu 09 | 0 | 0.0 | 108 ms | 0 |
| Thu 11 | 0 | 0.0 | 116 ms | 0 |
| Thu 13 | 0 | 0.0 | 236 ms | 0 |
| Thu 16 | 0 | 0.0 | 344 ms | 0 |
| Thu 18 | 0 | 0.0 | 439 ms | 0 |
| Thu 20 | 0 | 0.0 | 321 ms | 0 |
| Thu 22 | 0 | 0.0 | 395 ms | 0 |
| Fri 00 | 0 | 0.0 | 298 ms | 0 |
| Fri 01 | 0 | 0.0 | 334 ms | 0 |
| Fri 03 | 0 | 0.0 | 225 ms | 0 |
| Fri 05 | 0 | 0.0 | 487 ms | 0 |
| Fri 07 | 0 | 0.0 | 265 ms | 0 |
| Fri 09 | 0 | 0.0 | 456 ms | 0 |
| Fri 11 | 0 | 0.0 | 375 ms | 0 |
| Fri 13 | 0 | 0.0 | 271 ms | 0 |
| Fri 15 | 0 | 0.0 | 143 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 Embedly 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 Embedly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Embedly alerts to Slack, Discord or a webhook — free.
Embedly, at embed.ly, is one of the Cloud & developer services we monitor. Embedly delivers the ultra-fast, easy to use products and tools for richer sites and apps.
Embedly publishes an official status page at status.embed.ly; 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: 346 ms average, 75–898 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Embedly incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
346 ms on average over the last 24 hours (75–898 ms).
Yes, at https://status.embed.ly.
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 Embedly here at once, the problem is on Embedly'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 Embedly. 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.