Simwood logo

Is Simwood Down?

CommunicationLive status, outages, and incident history

No. Simwood is up right now.

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

OperationalChecked 3m agoLive · every 60s

Know the moment Simwood breaks

Simwood is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

How we know: the official Simwood status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Simwood Status Summary

As of 04:47 UTC on 14 November 2026, Simwood is operational. PulsAPI checked Simwood's official status page and found 9 of 9 components operational, with no active incidents. The latest incident, "999 and Vodafone reports", was on Nov 13, 2026 and lasted 6h 39m.

Cite as: PulsAPI, “Simwood status”, checked 14 November 2026, 04:47 UTC. https://www.pulsapi.com/services/simwood

Simwood Component Status

The main Simwood systems on this page. All 9 are operational right now.

9operational
API and Portal
Operational
Availability Zones (US) » New York
Operational
Availability Zones (US) » San Jose
Operational

6 more components tracked

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

Also tracking Availability Zones » London, Availability Zones » Manchester, Availability Zones » Slough, Operations Desk, SMS, Voice.

See all of them free

Component statuses may change independently during partial outages.

Recent Simwood Outages & Incidents

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

999 and Vodafone reportsResolved Nov 13, 2026 · 6h 39mResolved

We understand the Microsoft issue is much improved and while there are still reports of 999 delays, they are not telephony related. We are marking this incident resolved. --- [2026-11-13T11:37:37.118Z] (monitoring) Further reports suggest the 999 reports relate to an issue with retrieving patient records causing delays, rather than a telephony outage. We continue to monitor. --- [2026-11-13T11:15:59.516Z] (monitoring) There are anecdotal reports of a 999 and Vodafone outage linked to Microsoft’s issues. We are not seeing this in our own statistics and monitoring and suspect it may be regionally specific. We are however monitoring.

NCSC alert on critical PHP security issue (CVE-2026-109618 / CVE-2026-109619)Resolved Oct 22, 2026 · 24h 56mResolved

This incident has been resolved. --- [2026-10-22T09:58:14.291Z] (monitoring) You may have seen the NCSC alert about a critical security issue affecting PHP. This note explains what we have done. What the issue is: Two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, could allow an attacker to trigger an out-of-memory condition in PHP that corrupts memory. Under certain conditions, this could be exploited to run code remotely without logging in. The issue affects all supported versions of PHP. The PHP project has now released a fix. What we have done: • Audit and interim measures: On the morning of 21 October, as soon as we learned of the vulnerabilities, we audited every Simwood service that uses PHP. Where the PHP project recommended interim mitigations, we applied them, so affected services were protected before a fix existed. • Patching: The fix was released at 15:00 (UK time) on 21 October. We treated it as urgent and updated every affected service to the fixed version. • Verification: We then checked each service to confirm the fixed version was running and the service was working normally. Current position: Based on these actions, we believe our services are protected against these vulnerabilities and customer data remains secure. We will keep watching guidance from the NCSC and the PHP project, including any updates to products that bundle PHP, and act on it promptly. Do you need to do anything? You don't need to do anything about the Simwood services we provide. If you run PHP on your own systems, we recommend following the NCSC's advice: • find every PHP installation, internet-facing ones first; • update to the latest fixed version; • if you can’t update straight away, apply the PHP project’s temporary mitigations or take the application offline. If you have any questions, please contact our support team.

Simwood Uptime History

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

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Simwood Outage Reports

Problems reported by engineers using Simwood. 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 Simwood problems reported yet.

Something wrong with Simwood on your end?

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

About Simwood

Simwood posts its status at status.simwood.com. The page covers 9 components, among them API and Portal, New York (US East) and San Jose (US West). Past incidents and uptime for Simwood stay on this page, which helps when you want to know how often it has trouble.

Simwood Status FAQ

Is Simwood down right now?

The verdict at the top of this page comes from the latest poll of the official Simwood status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Simwood 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 Simwood recovers.

How do I check Simwood uptime history?

PulsAPI tracks Simwood uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Simwood changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Simwood outages?

PulsAPI reads the official Simwood status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Simwood components?

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

Can I get alerts when Simwood goes down?

Yes. Create a free account and subscribe to Simwood: 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 Simwood 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 Simwood problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Simwood?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Simwood 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 Simwood with the rest of your stack

4372+ 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