Is FactSet down?

Over the last 90 days, FactSet reported 100.00% uptime on its official status page. That figure is calculated from the public incident timeline at https://go.factset.com/status — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see FactSet's uptime history rolling forward in real time.

FactSet has had zero incidents reported on its status page so far in 2026 — that's the official record. Pingoru tracks the page every 5 minutes; if a new incident appears, we'll capture it within that window.

Pingoru hasn't recorded any FactSet incidents within our retention window. That doesn't mean FactSet has never had an outage — only that we haven't seen a new one cross our 5-minute polling cycle in the period we display. Sign up free and you'll be alerted on the first one we do detect.

FactSet has been quiet over the last 90 days — fewer than one reported incident per month. Sign up free to be alerted the moment that changes.

FactSet's official status page is https://go.factset.com/status. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

FactSet is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment FactSet reports a change. Current status is based on 0 tracked services.

We read https://go.factset.com/status directly, using FactSet's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Create a free Pingoru account and add FactSet as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Three common reasons: • A real FactSet incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real FactSet issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

We use FactSet's own status page at https://go.factset.com/status and cross-reference their homepage (https://www.factset.com). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

All tracked FactSet components are reporting operational. No incidents are currently affecting service.