User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
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 1 hr ago. Last stored result reached it in 51 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 10 | 0 | 0.0 | 63 ms | 0 |
| Mon 12 | 0 | 0.0 | 92 ms | 0 |
| Mon 14 | 0 | 0.0 | 98 ms | 0 |
| Mon 17 | 0 | 0.0 | 99 ms | 0 |
| Mon 19 | 0 | 0.0 | 66 ms | 0 |
| Mon 21 | 0 | 0.0 | 52 ms | 0 |
| Mon 23 | 0 | 0.0 | 75 ms | 0 |
| Tue 01 | 0 | 0.0 | 145 ms | 0 |
| Tue 03 | 0 | 0.0 | 123 ms | 0 |
| Tue 05 | 0 | 0.0 | 52 ms | 0 |
| Tue 08 | 0 | 0.0 | 93 ms | 0 |
| Tue 10 | 0 | 0.0 | 47 ms | 0 |
| Tue 12 | 0 | 0.0 | 35 ms | 0 |
| Tue 14 | 0 | 0.0 | 32 ms | 0 |
| Tue 16 | 0 | 0.0 | 40 ms | 0 |
| Tue 19 | 0 | 0.0 | 134 ms | 0 |
| Tue 21 | 0 | 0.0 | 131 ms | 0 |
| Tue 23 | 0 | 0.0 | 105 ms | 0 |
| Wed 01 | 0 | 0.0 | 116 ms | 0 |
| Wed 04 | 0 | 0.0 | 77 ms | 0 |
| Wed 06 | 0 | 0.0 | 131 ms | 0 |
| Wed 08 | 0 | 0.0 | 79 ms | 0 |
| Wed 10 | 0 | 0.0 | 89 ms | 0 |
| Wed 13 | 0 | 0.0 | 96 ms | 0 |
| Wed 15 | 0 | 0.0 | 73 ms | 0 |
| Wed 17 | 0 | 0.0 | 133 ms | 0 |
| Wed 19 | 0 | 0.0 | 48 ms | 0 |
| Wed 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 23 | 0 | 0.0 | 106 ms | 0 |
| Thu 02 | 0 | 0.0 | 58 ms | 0 |
| Thu 04 | 0 | 0.0 | 135 ms | 0 |
| Thu 06 | 0 | 0.0 | 99 ms | 0 |
| Thu 08 | 0 | 0.0 | 147 ms | 0 |
| Thu 10 | 0 | 0.0 | 72 ms | 0 |
| Thu 12 | 0 | 0.0 | 78 ms | 0 |
| Thu 14 | 0 | 0.0 | 156 ms | 0 |
| Thu 16 | 0 | 0.0 | 130 ms | 0 |
| Thu 18 | 0 | 0.0 | 51 ms | 0 |
| Thu 20 | 0 | 0.0 | 59 ms | 0 |
| Thu 21 | 0 | 0.0 | 90 ms | 0 |
| Thu 23 | 0 | 0.0 | 43 ms | 0 |
| Fri 02 | 0 | 0.0 | 127 ms | 0 |
| Fri 04 | 0 | 0.0 | 63 ms | 0 |
| Fri 06 | 0 | 0.0 | 40 ms | 0 |
| Fri 08 | 0 | 0.0 | 38 ms | 0 |
| Fri 10 | 0 | 0.0 | 53 ms | 0 |
| Fri 12 | 0 | 0.0 | 66 ms | 0 |
| Fri 14 | 0 | 0.0 | 65 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 Twingly 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 Twingly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Twingly alerts to Slack, Discord or a webhook — free.
Twingly, at twingly.com, is one of the News services we monitor. Twingly keeps track of updates from millions of online sources such as news, blogs, forums, reviews, and the dark web.
Twingly publishes an official status page at status.twingly.com; when we can read it, its incident level is folded into the status shown here.
Common problems for news services: news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms.
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: 68 ms average, 34–130 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Twingly incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
68 ms on average over the last 24 hours (34–130 ms).
Yes, at https://status.twingly.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For news services, watch for news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms. If many people report Twingly here at once, the problem is on Twingly'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 Twingly. 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.