Twingly logo

Is Twingly Down?

SaaSLive status, outages, and incident history

No. Twingly is up right now.

Every monitored Twingly system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment Twingly breaks

Twingly is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Twingly status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Twingly Component Status

The main Twingly systems on this page. All 10 are operational right now.

10operational
Blog Data collection
Operational
Blog LiveFeed API v5
Operational
Blog Search API v3
Operational

7 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Dark Web Search API, Data center STH, Forum Search API, News LiveFeed API, News Search API, Review Search API, VK Search API.

See all of them free

Component statuses may change independently during partial outages.

Recent Twingly Outages & Incidents

Incident history from the official Twingly status page, including resolution updates.

News LiveFeed and Search API delaysResolved Aug 28, 2026 · 3h 11mResolved

The system has caught up with the delayed article deliveries and we are back to normal operational status. --- [2026-08-28T11:48:05.708+02:00] (monitoring) The root cause of the outage has been fixed and our systems are catching up with news article deliveries. We continue to monitor the situation. --- [2026-08-28T11:13:39.971+02:00] (identified) We have identified an outage affecting: News Search API News LiveFeed API Historical data in the News Search is still available. Delivery of recent articles will be delayed until the outage has been resolved.

Service downtime for News Search and Livefeed (260713-260714)Resolved Jul 14, 2026 · -663 minResolved

On 2026-07-13, at approximately 22:40, the News Search and Livefeed APIs started experienced service disruptions due to disk issues with one of our servers. On 2026-07-14, at 08:40, the issues were resolved, and the system started to deliver new articles through the APIs again. No new articles were being delivered through the News Search and Livefeed APIs during this time. We expect most articles published during this time to be delivered as the system is catching up, however, some articles may be lost. We're currently setting up more extensive monitoring checks to ensure this problem doesn't occur again. We apologize for any inconvenience this may have caused.

Twingly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Twingly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live Twingly Outage Reports

Problems reported by engineers using Twingly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Twingly problems reported yet.

Something wrong with Twingly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Twingly

Twingly exposes 10 monitored components on its status page at status.twingly.com — Blog Search API v3, Blog LiveFeed API v5 and Forum Search API among them. Follow Twingly downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Twingly uptime at 99.97%. Response times, incident history, and SLA tracking for Twingly are available on the PulsAPI dashboard.

Twingly Status FAQ

Is Twingly down right now?

The verdict at the top of this page comes from the latest poll of the official Twingly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Twingly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Twingly recovers.

How do I check Twingly uptime history?

PulsAPI tracks Twingly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.97%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Twingly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Twingly outages?

PulsAPI reads the official Twingly status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Twingly components?

Yes. PulsAPI monitors 10 individual Twingly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Twingly goes down?

Yes. Create a free account and subscribe to Twingly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Twingly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Twingly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Twingly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Twingly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Twingly with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services