User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 58 min ago. Last stored result reached it in 898 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 910 ms | 0 |
| Mon 23 | 0 | 0.0 | 866 ms | 0 |
| Tue 01 | 0 | 0.0 | 762 ms | 0 |
| Tue 03 | 0 | 0.0 | 875 ms | 0 |
| Tue 05 | 0 | 0.0 | 821 ms | 0 |
| Tue 07 | 0 | 0.0 | 699 ms | 0 |
| Tue 09 | 0 | 0.0 | 794 ms | 0 |
| Tue 12 | 0 | 0.0 | 678 ms | 0 |
| Tue 14 | 0 | 0.0 | 775 ms | 0 |
| Tue 16 | 0 | 0.0 | 789 ms | 0 |
| Tue 18 | 0 | 0.0 | 795 ms | 0 |
| Tue 21 | 0 | 0.0 | 902 ms | 0 |
| Tue 23 | 0 | 0.0 | 709 ms | 0 |
| Wed 01 | 0 | 0.0 | 804 ms | 0 |
| Wed 03 | 0 | 0.0 | 833 ms | 0 |
| Wed 05 | 0 | 0.0 | 890 ms | 0 |
| Wed 08 | 0 | 0.0 | 778 ms | 0 |
| Wed 10 | 0 | 0.0 | 826 ms | 0 |
| Wed 12 | 0 | 0.0 | 918 ms | 0 |
| Wed 14 | 0 | 0.0 | 863 ms | 0 |
| Wed 16 | 0 | 0.0 | 820 ms | 0 |
| Wed 18 | 0 | 0.0 | 646 ms | 0 |
| Wed 21 | 0 | 0.0 | 788 ms | 0 |
| Wed 23 | 0 | 0.0 | 766 ms | 0 |
| Thu 01 | 0 | 0.0 | 863 ms | 0 |
| Thu 03 | 0 | 0.0 | 855 ms | 0 |
| Thu 05 | 0 | 0.0 | 919 ms | 0 |
| Thu 07 | 0 | 0.0 | 606 ms | 0 |
| Thu 09 | 0 | 0.0 | 1012 ms | 0 |
| Thu 11 | 0 | 0.0 | 900 ms | 0 |
| Thu 13 | 0 | 0.0 | 824 ms | 0 |
| Thu 16 | 0 | 0.0 | 754 ms | 0 |
| Thu 18 | 0 | 0.0 | 850 ms | 0 |
| Thu 20 | 0 | 0.0 | 843 ms | 0 |
| Thu 22 | 0 | 0.0 | 786 ms | 0 |
| Fri 00 | 0 | 0.0 | 853 ms | 0 |
| Fri 02 | 0 | 0.0 | 820 ms | 0 |
| Fri 04 | 0 | 0.0 | 776 ms | 0 |
| Fri 06 | 0 | 0.0 | 793 ms | 0 |
| Fri 08 | 0 | 0.0 | 744 ms | 0 |
| Fri 10 | 0 | 0.0 | 841 ms | 0 |
| Fri 12 | 0 | 0.0 | 926 ms | 0 |
| Fri 14 | 0 | 0.0 | 841 ms | 0 |
| Fri 16 | 0 | 0.0 | 675 ms | 0 |
| Fri 18 | 0 | 0.0 | 760 ms | 0 |
| Fri 20 | 0 | 0.0 | 664 ms | 0 |
| Fri 22 | 0 | 0.0 | 784 ms | 0 |
| Sat 00 | 0 | 0.0 | 898 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 Lordicon 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 Lordicon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lordicon alerts to Slack, Discord or a webhook — free.
We track Lordicon (lordicon.com) as part of the Productivity group. Lordicon is an animated icon library with the 49,000+ premium and free animated icons, perfect for enhancing web, mobile, or content design projects.
Lordicon publishes an official status page at status.lordicon.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 797 ms average, 664–926 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 Lordicon incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
797 ms on average over the last 24 hours (664–926 ms).
Yes, at https://status.lordicon.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Lordicon here at once, the problem is on Lordicon'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 Lordicon. 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.