OutSystems logo

Is OutSystems Down?

SaaSLive status, outages, and incident history

Partly. Some of OutSystems is down.

OutSystems is in a partial outage as of October 5, 2026. Some components are down and others are still running, so check the list below to see whether your region or feature is affected.

Partial OutageChecked just nowLive · 60s while moving1 active incident

Don't find out like this next time

You searched to find out OutSystems 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 OutSystems 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

OutSystems Component Status

3 of 80 OutSystems components are impaired. Worst problems listed first.

3major outage77operational
ODC - Customer Apps & Data » Middle East / UAE
Major Outage
ODC - Identity & Access Management » Middle East / UAE
Major Outage
ODC - Platform and Portal » Middle East / UAE
Major Outage

77 more components tracked

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

Also tracking Mentor » Africa / Cape Town, Mentor » Asia Pacific / Hong Kong, Mentor » Asia Pacific / Jakarta, Mentor » Asia Pacific / Mumbai, Mentor » Asia Pacific / Seoul, Mentor » Asia Pacific / Singapore, Mentor » Asia Pacific / Sydney, Mentor » Asia Pacific / Tokyo, Mentor » Canada / Central, Mentor » Europe / Frankfurt, Mentor » Europe / Ireland, Mentor » Europe / London, and 65 more.

See all of them free

Component statuses may change independently during partial outages.

Recent OutSystems Outages & Incidents

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

Issue Affecting Application Publishing in Asia Pacific, Mumbai regionStarted Oct 5, 2026Investigating

We have identified the cause of the issue affecting application publishing in ODC in the Asia Pacific, Mumbai region. The issue was linked to a fault in a supporting service involved in retrieving application configurations, and corrective action has now been applied. Error rates have returned to normal, and users should now be able to publish applications from ODC Studio. We are closely monitoring the platform and confirming full recovery with affected users, and will provide a further update once the incident is fully resolved. --- [2026-10-05T10:26:12.401Z] (investigating) We are investigating an issue affecting application publishing in ODC in the Asia Pacific, Mumbai region. Users may experience intermittent failures when publishing applications from ODC Studio, with an error related to fetching application configurations. Our team is actively investigating the cause and will provide updates as more information becomes available.

Incident affecting data preview in ODC Studio and runtime applicationsResolved Sep 29, 2026 · 24h 43mResolved

The issue that prevented ODC users across multiple regions from previewing data in ODC Studio, and that may also have caused errors in application runtime, has been resolved. A fix was applied and our team has monitored the platform to confirm full recovery. Data preview is working as expected and all services are operating normally. We apologise for any disruption caused and thank you for your patience. --- [2026-09-29T16:52:18.723Z] (monitoring) The fix has now been fully applied across all affected regions, and error rates have returned to normal levels. Users should once again be able to preview data in ODC Studio and access their applications as expected. We are continuing to monitor the platform closely and are confirming full recovery with affected users. We will provide a further update once we have confirmed the incident is fully resolved. --- [2026-09-29T11:36:32.530Z] (identified) We have identified the cause of this issue as a recent database authentication update that failed validation during rollout. The update has been reverted, and a fix is currently being deployed. As the fix is applied across affected regions, users may still experience difficulty previewing application data in ODC Studio or encounter errors when accessing their applications. We will provide an update as soon as more information becomes available. --- [2026-09-29T10:49:01.927Z] (investigating) We are investigating an issue affecting ODC users across multiple regions. Users are currently unable to preview data in ODC Studio and may also encounter errors in application runtime. The issue is associated with the error message: "FATAL: PAM authentication failed for user "osruntime"". Our engineering team is actively investigating the issue, and we will provide an update as soon as more information is available.

Incident affecting Personal Edition login in Asia Pacific (Singapore)Resolved Sep 29, 2026 · 28h 39mResolved

Between September 17th and September 30th, 2026, a limited number of ODC Personal Edition users in the Asia Pacific \(Singapore\) region were unable to log in to their Personal Editions and encountered the error message "Login with external provider failed." The issue was caused by a configuration update related to the external login provider that did not apply correctly for the affected Personal Editions, leaving them unable to complete the login process. It was detected through user reports. Once the cause was identified, our team restored the correct configuration for the affected Personal Editions, and users were able to log in again. Service was fully restored on September 30th. We are continuing to investigate why the configuration update did not apply correctly, so that we can prevent it from happening again. We apologise for any disruption caused and thank you for your patience. --- [2026-09-30T13:40:12.424Z] (resolved) The issue affecting login to Personal Environments in the Asia Pacific (Singapore) region has been resolved. The fix has now been applied to all affected accounts, and users are able to log in again without encountering the "Login with external provider failed" error. We apologise for any disruption caused and thank you for your patience. --- [2026-09-29T18:23:04.872Z] (identified) We have applied the fix to a first set of affected accounts in the Asia Pacific (Singapore) region and confirmed that users on those accounts are able to log in to their Personal Environments again. The remaining affected accounts have not yet been updated, and users on those accounts will continue to see the "Login with external provider failed" error until the fix is applied. We will provide a further update as more information becomes available. --- [2026-09-29T11:41:38.879Z] (identified) We have identified the cause of the issue affecting login to Personal Environments in the Asia Pacific (Singapore) region. The problem is related to a configuration issue with the external login provider for affected accounts. Some users may still experience the previously reported "Login with external provider failed" error while the fix is completed across all affected accounts. Our team is actively working to finish the resolution and will provide a further update once more information is available. --- [2026-09-29T09:00:49.718Z] (investigating) We are investigating an issue impacting ODC Personal Editions in the Asia Pacific (Singapore) region. Users may be unable to log in to their personal environments and may encounter the error message "Login with external provider failed." Our team is actively investigating the issue and will provide further updates as soon as more information becomes available.

OutSystems Uptime History

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

Uptime history59 days observed
Aug 899.96% average · 59 days with incidentsOct 5

Live OutSystems Outage Reports

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

Are you seeing OutSystems problems too?

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

About OutSystems

OutSystems exposes 84 monitored components on its status page at status.outsystems.com — Home, Mobile Application Build Service and US East / Virginia among them. Follow OutSystems downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

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

OutSystems Status FAQ

Is OutSystems down right now?

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

How do I check OutSystems uptime history?

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

How fast does PulsAPI detect OutSystems outages?

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

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

Can I get alerts when OutSystems goes down?

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

Is there a free way to monitor OutSystems?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so OutSystems 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 OutSystems 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