Osuosl logo

Is Osuosl Down?

SaaSLive status, outages, and incident history

Degraded. Osuosl is up but having problems.

Osuosl is reporting degraded performance as of November 9, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s2 active incidents

Don't find out like this next time

You searched to find out Osuosl was down. Next time we tell you, usually before your customers do, and always before you think to check.

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

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

Status report

Osuosl Status Summary

As of 21:03 UTC on 9 November 2026, Osuosl is reporting degraded performance. PulsAPI checked Osuosl's official status page and found 1 of 9 components operational, with 2 active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Osuosl, counting degraded performance as up. The latest incident, "Websites slow or unavailable: shared MySQL database", was on Nov 8, 2026 and lasted 31 min.

Cite as: PulsAPI, “Osuosl status”, checked 9 November 2026, 21:03 UTC. https://www.pulsapi.com/services/osuosl

Osuosl Component Status

8 of 9 Osuosl components are impaired. Worst problems listed first.

8degraded1operational
Core IPv4 Network [Salem, OR]
Degraded
Core IPv6 Network [Salem, OR]
Degraded
DNS [Madison, WI]
Degraded

6 more components tracked

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

Also tracking DNS [Salem, OR], FTP Mirrors [Chicago, IL], FTP Mirrors [New York, NY], FTP Mirrors [Salem, OR], Mail Relays [Salem, OR], Internal Monitoring [Salem, OR].

See all of them free

Component statuses may change independently during partial outages.

Recent Osuosl Outages & Incidents

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

Websites slow or unavailable: shared MySQL databaseResolved Nov 8, 2026 · 31 minResolved

From about 8:24 AM PST (16:24 UTC), one of our shared MySQL database servers was overloaded, so websites that use it loaded slowly or showed database errors. Other sites on our shared web hosting were also slow, because their web servers were stuck waiting on this database. Affected: - phpBB websites and services, including the forums, blog and Area51 - eLinux.org - Ogre3D's website, forum and wiki - the Amahi wiki and blog - the BusyBox bug tracker - the Mycroft Project - SeaMonkey updates - OpenID Foundation sites, the OpenPOWER Foundation's Nextcloud and our Etherpad - other websites on our shared web hosting We found the source of the load and restarted the database service. Service has been restored for most sites as of 10:17 AM PST (18:17 UTC); Ogre3D's sites are still unavailable while we work with that project. Our other database servers, mail, DNS and the FTP mirrors were not affected. We are monitoring the server and will post another update.

osuosl.org HTTPS certificate not trusted on Amazon Linux and some Java runtimesStarted Nov 4, 2026Investigating

Some clients can no longer verify the HTTPS certificate on most of our osuosl.org sites, including the ftp.osuosl.org mirrors (ftp-nyc, ftp-chi and ftp-osl). Downloads fail with "unable to get local issuer certificate" (curl error 60) or a Java "unable to find valid certification path" error. Who is affected: - Amazon Linux 2023 and Amazon Linux 2 hosts with the latest ca-certificates package (ALAS2023-2026-3306, ALAS2-2026-4037), which removed every eMudhra root. - Java runtimes whose trust store has dropped eMudhra's emSign Root CA - G1. - Anything else that has removed all eMudhra roots, such as a corporate trust policy. Not affected: Web browsers and most Linux distributions still trust this certificate, and the sites themselves are up. What happened: The *.osuosl.org certificate most of our sites use comes from InCommon and chains to eMudhra's emSign Root CA - G1. After last month's eMudhra key compromise, which involved a different eMudhra hierarchy, some vendors removed all eMudhra roots, including this one. The Jenkins project has temporarily taken our mirrors out of its download rotation for this reason. What we're doing: We are moving the ftp.osuosl.org mirrors to Let's Encrypt certificates, which we expect to finish in the next couple of weeks, and will post here when they have switched. Our other osuosl.org certificates will move off eMudhra before the current certificate expires in February. If you are affected and need help in the meantime, email support@osuosl.org.

Critical Linux kernel TCP vulnerability (CVE-2026-98432)Started Nov 1, 2026Investigating

A critical flaw in the Linux kernel's IPv4 TCP code (CVE-2026-98432, CVSS 9.8) lets a remote attacker with no login crash the kernel, and possibly run code, by sending crafted packets to any open TCP port. If your project runs Linux on an OpenStack VM or a server that you manage yourself, please install your distribution's fixed kernel as soon as it is available and reboot into it. Who needs to act: - Projects that manage their own OpenStack VMs or colocated servers running Linux. Every distribution is affected. - Hosts that OSL manages for you: we have already applied the interim mitigation below and will reboot them onto fixed kernels in our normal maintenance windows, announced here as usual. Fix status (Nov 1): - Debian: fixed. Debian 13 in 6.12.113-1 (DSA-6568-1), Debian 12 in 6.1.190-1 (DLA-4841-1). - AlmaLinux 8, 9 and 10: fixed kernels are in the testing repository (4.18.0-553.180.2, 5.14.0-687.61.2, 6.12.0-211.69.2) and not yet in the regular updates. - RHEL and Ubuntu: no fixed kernel yet; Red Hat rates the flaw Critical and Ubuntu has fixes in progress. For other distributions, including those built from RHEL, check your vendor's security notices. Interim mitigation: Until you can reboot onto a fixed kernel, drop incoming IPv4 TCP packets that carry IP options, which normal traffic does not use. Red Hat's bulletin gives this nftables rule (run as root; it lasts until the next reboot): nft add table inet cve_2026_98432 nft add chain inet cve_2026_98432 input '{ type filter hook input priority -310 ; policy accept ; }' nft add rule inet cve_2026_98432 input ip protocol tcp ip hdrlength gt 5 counter drop If the VM runs Docker or other containers, add the same chain and rule with "forward" in place of "input" so container ports are covered too. Remove it after rebooting onto the fixed kernel with: nft delete table inet cve_2026_98432 Red Hat's bulletin: https://access.redhat.com/security/vulnerabilities/RHSB-2026-016 If you are unsure whether you are affected or need help, email support@osuosl.org. --- [2026-11-02T21:47:34.036Z] (600) Update (Nov 2): AlmaLinux's fixed kernels for CVE-2026-98432 are now in the regular updates for AlmaLinux 8 (4.18.0-553.182.1), 9 (5.14.0-687.64.1) and 10 (6.12.0-211.72.1). If your VM runs AlmaLinux, run "dnf update kernel" and reboot into the new kernel; you can then remove the interim nftables rule. For other distributions, check your vendor's security notices. On our side, the OpenStack servers move onto fixed kernels on Tuesday, November 3 (live migrations, no restart) and Thursday, November 5 (VMs restarted once), in the two maintenance notices on this page. Those reboots update our servers only, so VMs still need their own kernel update. If you need help, email support@osuosl.org. --- [2026-11-04T21:02:21.305Z] (600) Update (Nov 4): Our own internet-facing servers move onto fixed kernels in two maintenance windows. On Thursday, November 12, 11:00 AM – 3:00 PM PST (19:00 – 23:00 UTC), we reboot our CI runners and OSL services. On Friday, November 13, 10:00 AM – 1:00 PM PST (18:00 – 21:00 UTC), we reboot the project sites, mailing lists and FTP mirrors we host. The firewall rule on those servers stays in place until then. Thursday: https://status.osuosl.org/pages/maintenance/526712bf10cd4e587b000014/6aeb9bd7f7bb4b038d276f4d Friday: https://status.osuosl.org/pages/maintenance/526712bf10cd4e587b000014/6aeb9bf5b435fe0422769f92 These reboots update our servers only. If your VM runs AlmaLinux, run "dnf update kernel" and reboot into the new kernel, as in our Nov 2 update. If you need help, email support@osuosl.org.

Upcoming maintenance

Announced by Osuosl. Planned work, not an outage.

Kernel Security Reboots for CVE-2026-98432 – Thursday, Nov 12, 11:00 AM–3:00 PM PST (19:00–23:00 UTC)Scheduled for Nov 12, 2026 · 4h 0mScheduled

Scheduled Maintenance

Kernel Security Reboots for CVE-2026-98432 – Friday, Nov 13, 10:00 AM–1:00 PM PST (18:00–21:00 UTC)Scheduled for Nov 13, 2026 · 3h 0mScheduled

Scheduled Maintenance

Osuosl Uptime History

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

Uptime history91 days observed
Aug 11100.00% average · 9 days with incidentsNov 9

Going further back: Osuosl uptime by month and every recorded Osuosl outage.

Live Osuosl Outage Reports

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

Are you seeing Osuosl problems too?

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

About Osuosl

Osuosl maintains a public status page at status.osuosl.org reporting overall service health. Follow Osuosl downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

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

Osuosl Status FAQ

Is Osuosl down right now?

The verdict at the top of this page comes from the latest poll of the official Osuosl 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 Osuosl 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 Osuosl recovers.

How do I check Osuosl uptime history?

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

How fast does PulsAPI detect Osuosl outages?

PulsAPI reads the official Osuosl 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 Osuosl components?

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

Can I get alerts when Osuosl goes down?

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

Is there a free way to monitor Osuosl?

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

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